Revision control
Copy as Markdown
Other Tools
# Parameters
## Overview
See the gecko_taskgraph parameters documentation.
## Comm Push Information
These parameters correspond to the repository and revision of the comm-central
repository to checkout. All parameters are required except for comm_base_ref,
which may sometimes be set to `None` (when this happens, it will be defaulted
to the repository's default branch), and comm_head_git_repository /
comm_head_git_rev, which are only set when the git commit is recorded in the
Mercurial changeset.
`comm_base_repository`
: The repository from which to do an initial clone, utilizing any available
`comm_base_rev`
: The previous revision before `comm_head_rev` got merged into.
`comm_base_ref`
: Reference where `comm_head_rev` got merged into. It is usually a branch or a tag.
`comm_head_repository`
: The repository containing the changeset to be built. This may differ from
`comm_base_repository`.
`comm_head_rev`
: The revision to check out; this can be a short revision string.
`comm_head_git_repository`
: Optionally, the git repository backing `comm_head_repository` when it's a
Mercurial repository.
`comm_head_git_rev`
: Optionally, the git commit corresponding to `comm_head_rev` when it's in a
Mercurial repository.
`comm_head_ref`
: This is the same as `head_rev`.
`comm_src_path`
: This will effectively always be "comm/". It's used in
`comm_taskgraph.files_changed.get_files_changed_extended` to handle multiple
VCS repositories without hardcoding parameters.