The partial generation code checks the URLs of the source versions. To allow
building partials from staging releases, allow the staging CDN when generating
partials.
Differential Revision: https://phabricator.services.mozilla.com/D5710
--HG--
extra : moz-landing-system : lando
All the required on-push jobs will be pulled into the graph as dependencies.
The effect of this is to remove the upload symbols and generated sources tasks
from the release promotion graphs.
Differential Revision: https://phabricator.services.mozilla.com/D8306
--HG--
extra : moz-landing-system : lando
These were originally built in the promotion phase because they are multi-l10n
builds and the L10n information wasn't stored in-tree. Now that the information
is in-tree, there is no reason to delay building them.
Differential Revision: https://phabricator.services.mozilla.com/D8305
--HG--
extra : moz-landing-system : lando
- `beetmover-cdns` should always use `:beetmover:action:push-to-releases`,
not every task that happens to be part of the push graph.
- All other beetmover scopes only change depending whether the builds is
a nightly build, or on a production branch.
Differential Revision: https://phabricator.services.mozilla.com/D8304
--HG--
extra : moz-landing-system : lando
The phase of a task doesn't depend on which phase graph it is being generated in.
Differential Revision: https://phabricator.services.mozilla.com/D8303
--HG--
extra : moz-landing-system : lando
This also requires the 64-bits rust compiler and some build system
tweaks.
And since we make the 32-bits builds cross-compiles on CI, we also need
to adjust the MSVC build mozconfigs such that the host compiler points
to the right MSVC cl. Likewise, the DIA SDK is used for host things, so
use the 64-bits version or it.
Differential Revision: https://phabricator.services.mozilla.com/D7845
--HG--
extra : moz-landing-system : lando
Depending on chunking, some mochitest-browser-chrome chunks are reaching the
time limit of 60 minutes on macosx64/debug. With more chunks, hopefully we can
avoid this for now.
Differential Revision: https://phabricator.services.mozilla.com/D8287
--HG--
extra : moz-landing-system : lando
Summary: Switch to autograph mar hash signing.
Test Plan:
X pin nightly updates
_ autoland this patch
_ uplift this patch to central
_ wait for nightlies to spin
_ test nightlytest channel
_ unpin nightly updates
Reviewers: catlee
Tags: #secure-revision
Bug #: 1471197
Differential Revision: https://phabricator.services.mozilla.com/D8251
--HG--
extra : rebase_source : 755efd3d2cb350d9d70bb7841a0c173b6244384f
This commit also removes dwarf-exceptions from the x64 build.
sjlj exceptions are needed on x86 because there is a bug currently involving
SEH exceptions on x86. However on x64 there is not, so we can use the
default SEH and get rid of dwarf exceptions. Additionally, to use SEH
exceptions, we need to -fuse-cxa-atexit
Differential Revision: https://phabricator.services.mozilla.com/D7759
--HG--
extra : moz-landing-system : lando
This commit also removes dwarf-exceptions from the x64 build.
sjlj exceptions are needed on x86 because there is a bug currently involving
SEH exceptions on x86. However on x64 there is not, so we can use the
default SEH and get rid of dwarf exceptions. Additionally, to use SEH
exceptions, we need to -fuse-cxa-atexit
Differential Revision: https://phabricator.services.mozilla.com/D7759
--HG--
extra : moz-landing-system : lando
pip 18.0.1 and recent pipenv don't work together. Until a new pipenv is released, this is a workaround.
Differential Revision: https://phabricator.services.mozilla.com/D7991
--HG--
extra : moz-landing-system : lando
This makes enabling DMD at runtime in automation opt-in via a '--dmd' param.
Currently this is enabled via the 'awsy-dmd-e10s' and 'awsy-base-dmd-e10s'
tests.
--HG--
extra : rebase_source : 0371dca4d99197e7f0a37dfcd3763903f807b7b0
This also requires the 64-bits rust compiler and some build system
tweaks.
Differential Revision: https://phabricator.services.mozilla.com/D7845
--HG--
extra : moz-landing-system : lando
This patch removes linux64-jsdcov from the available builds on taskcluster along with any hacks used to run it. It also removes any 'coverage' entries that were added to skip tests.
Differential Revision: https://phabricator.services.mozilla.com/D7919
--HG--
extra : moz-landing-system : lando
This duplicates all the mochitest, based tests except with
dom.serviceWorkers.parent_intercept set to true. For now they are only run on
mozilla-central with linux64/debug.
Differential Revision: https://phabricator.services.mozilla.com/D7641
--HG--
extra : moz-landing-system : lando
This duplicates all the mochitest, based tests except with
dom.serviceWorkers.parent_intercept set to true. For now they are only run on
mozilla-central with linux64/debug.
Differential Revision: https://phabricator.services.mozilla.com/D7641
--HG--
extra : moz-landing-system : lando
The cctools-port linker links against libraries from clang (for LTO),
which have different SONAMEs depending on the clang version. Which means
the linker needs to be used along the same version of clang it was built
against. Thus we also make it depend on linux64-clang-7.
But changing the dependency is not enough, cf. bug 1471905, so also
touch its build script, which it turns out, we need to do anyways
because llvm-dsymutil was renamed to dsymutil.
Relatedly, all toolchains that are built using cctools-port need to use
linux64-clang-7 too.
Building compiler-rt 7 with the OSX 10.11 SDK fails because of some
newer APIs being used in compiler-rt for xray, but this is not a feature
we use, so disable that.
Differential Revision: https://phabricator.services.mozilla.com/D6766
The previous code split a lot of logic between the update and download
parts, and exposed two different mach commands. In order to simplify
things it's better to have a single entry point for manifest download
and update, and ensure that's called consistently.
Differential Revision: https://phabricator.services.mozilla.com/D7497
--HG--
extra : moz-landing-system : lando
If a packaging task ended up being retried for any reason, the downstream
docker tasks that depended on them would fail, since they were hard-coding the
artifacts from the initial run.
Differential Revision: https://phabricator.services.mozilla.com/D7364
--HG--
extra : moz-landing-system : lando
We don't apply schema defaults, since when `taskgraph.fast`, we skip validation --
which if we were using the result of applying defaults would mean that
behavior changes when we skip validation.
Differential Revision: https://phabricator.services.mozilla.com/D7381
--HG--
extra : moz-landing-system : lando
Pushing on a CLOSED TREE because this is fixing the grcov Mac toolchain task.
--HG--
extra : histedit_source : be97081d5eec36dea7d25680c2590282ebf8dab2
This duplicates all the reftest tasks except with
dom.serviceWorkers.parent_intercept set to true. For now they are only run on
mozilla-central with linux64/debug.
Depends on D7480
Differential Revision: https://phabricator.services.mozilla.com/D7481
--HG--
extra : moz-landing-system : lando
This adds a transform which will evaluate the 'serviceworker-e10s' key. If
False, the task is returned as is. If True, the task is run with the
'dom.serviceWorkers.parent_intercept' pref enabled. If 'both' the task is split
into two tasks, one with the pref, and one without.
Differential Revision: https://phabricator.services.mozilla.com/D7480
--HG--
extra : moz-landing-system : lando
There are a few external repos that hold copies of robustcheckout
in various places, mainly on release engineering infrastructure
that has been moved to GitHub. We should document those locations
in the same place we document the upgrade steps for Mercurial in
CI.
Differential Revision: https://phabricator.services.mozilla.com/D6989
--HG--
extra : moz-landing-system : lando
about:buildconfig on Thunderbird shows an incorrect mercurial source URL
that's a comm- repo, but a mozilla- changeset revision.
For Taskcluster builds at least, MOZ_SOURCE_CHANGESET is set as an environment
variable by mozharness. During the build, build/variables.py writes out
source-repo.h with a few defines, including MOZ_SOURCE_URL that gets picked
up by buildconfig.html.
Differential Revision: https://phabricator.services.mozilla.com/D7151
--HG--
extra : moz-landing-system : lando
The cctools-port linker links against libraries from clang (for LTO),
which have different SONAMEs depending on the clang version. Which means
the linker needs to be used along the same version of clang it was built
against. Thus we also make it depend on linux64-clang-7.
But changing the dependency is not enough, cf. bug 1471905, so also
touch its build script, which it turns out, we need to do anyways
because llvm-dsymutil was renamed to dsymutil.
Relatedly, all toolchains that are built using cctools-port need to use
linux64-clang-7 too.
Building compiler-rt 7 with the OSX 10.11 SDK fails because of some
newer APIs being used in compiler-rt for xray, but this is not a feature
we use, so disable that.
Differential Revision: https://phabricator.services.mozilla.com/D6766
--HG--
rename : build/build-clang/clang-6-macosx64.json => build/build-clang/clang-7-macosx64.json
rename : taskcluster/scripts/misc/build-clang-6-linux-macosx-cross.sh => taskcluster/scripts/misc/build-clang-7-linux-macosx-cross.sh
extra : moz-landing-system : lando
The release-update-verify-config task requires that the versions passed
to it match up with what's been released. The version of Thunderbird
does not necessarily match the Gecko version it's based on.
Depends on D6509
Differential Revision: https://phabricator.services.mozilla.com/D6510
--HG--
extra : moz-landing-system : lando
The previous code split a lot of logic between the update and download
parts, and exposed two different mach commands. In order to simplify
things it's better to have a single entry point for manifest download
and update, and ensure that's called consistently.
Differential Revision: https://phabricator.services.mozilla.com/D7497
