No builds other than vanilla opt and debug builds are supported by the artifact
code currently, so prevent variant builds from being replaced by artifact builds
by modifying mozharness' replacement logic to replace a build with an artifact
build only when it is a regular opt or debug build or when specified by a
config.
MozReview-Commit-ID: KUUgrbga53l
Without the use of an upstream the first repo cloned on a machine will
be cached. If a subsequent job references a different repo, it may have
to pull thousands of changesets because those changesets aren't part of
the initially-cloned repo. This is why the --upstream feature to
robustclone exists and is why it uses the mozilla-unified repo.
The mozilla-unified repo is a superset of central, aurora, beta, release,
etc. So by cloning it, you get changesets for all of the repos at the
time of the clone. When a subsequent job comes along and requests
a changeset from a different repo, you likely only need to fetch data
for a handful of changesets, not thousands.
This change adds the upstream url config for all fx_desktop_build jobs,
ensuring it is used. A redundant config entry for the try repo has been
removed as well.
MozReview-Commit-ID: 3EL7aSXS4AG
I'm not a fan of introducing a new configuration flags (and not
knowing where or how to document it!), but there's a clear need for
configuration in the absence of a documented way to add a coherent
"artifact build dimension" akin to "opt/debug". I like adding a
subtle tri-state flag even less, but I tried this with two flags
(ignore and build-variant) and it was worse, so I'm rolling with a
tri-state flag.
MozReview-Commit-ID: KTNvacTBUXB
Rather than clearing actions in volatile_config, add in actions from the artifact config's
default_actions. Incompatible actions are then skipped based on 'forced_artifact_build'
config value.
MozReview-Commit-ID: IZuDvxcQ7cN
Check try message for --artifact even if fx_desktop_build.py is run with
--skip-buildbot-actions
We can't rely on buildbot config. Add checks to TryToolsMixin._extract_try_message so
that it works even if self.buildbot_config is None.
MozReview-Commit-ID: 1xErjuOArBe
Override actions specified in TC task definition with default_actions from
artifact config
Clear MOZ_SIGN_CMD when enable_signed is set to False.
MozReview-Commit-ID: FmI6lu5EKWg
Override actions specified in TC task definition with default_actions from
artifact config
Clear MOZ_SIGN_CMD when enable_signed is set to False.
MozReview-Commit-ID: FmI6lu5EKWg
Now that the MercurialVCS VCS tool does things optimally, we no longer
need to use hgtool!
Again, this will effectively require a modern Mercurial version or
things will fail.
MozReview-Commit-ID: 9SM9qfYGlU6
Now that the MercurialVCS VCS tool does things optimally, we no longer
need to use hgtool!
Again, this will effectively require a modern Mercurial version or
things will fail.
MozReview-Commit-ID: 9SM9qfYGlU6
This adds a mozharness action, only run in TaskCluster, to fetch secrets from
the TaskCluster secrets API via the TaskCluster Proxy.
It requires that the SCM level of the build be passed in with the --scm-level
argument, defaulting to 1 (try)
MozReview-Commit-ID: C3rvOPF6Bm1
This adds a mozharness action, only run in TaskCluster, to fetch secrets from
the TaskCluster secrets API via the TaskCluster Proxy.
It requires that the SCM level of the build be passed in with the --scm-level
argument, defaulting to 1 (try)
MozReview-Commit-ID: C3rvOPF6Bm1
The psutil extension gets built on windows build machines during configure,
but that step only runs consistently after a clobber. This patch installs
psutil from a wheel in the mozharness virtualenv so it's available in
mozharness independent of what happens in the build.
