author Mike Hommey <>
Wed, 06 Mar 2019 22:48:05 +0000
changeset 520608 0d70e7e3302091699c769aa75d7389b1b3c2b5a8
parent 517085 7723ab72d5063523a849637b63475a34e4b3dd2e
child 521315 a2e7f5c935da4e03d9734b03f43ac62279a1df6b
permissions -rw-r--r--
Bug 1530908 - Don't use different mozconfigs for artifact builds. r=chmanchester Artifact mozconfigs are not necessarily up-to-date wrt changes to the nightly mozconfigs, and all in all, shouldn't be much different from them. It's just better to use the nightly mozconfigs (or beta on beta, etc.) and make the mozconfigs themselves handle the few things that need to be different when the USE_ARTIFACT environment is set (which is now consistently set by taskcluster) This does have the side effect of turning builds that actually don't support artifact builds red when using --artifact on try, instead of having them silently not be artifact builds as currently happens. Depends on D21314 Differential Revision:

# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at

# Common mozconfig for official builds.
# Add options to this file that will be inherited by all in-tree mozconfigs.
# This is useful for eg try builds with nondefault options that apply to all
# architectures, though note that if you want to override options set in
# another mozconfig file, you'll need to use mozconfig.common.override instead
# of this file.

if test -n "$USE_ARTIFACT"; then
. "$topsrcdir/build/mozconfig.artifact.automation"

mk_add_options AUTOCLOBBER=1

ac_add_options --enable-crashreporter

# Disable enforcing that add-ons are signed by the trusted root

ac_add_options --enable-js-shell

. "$topsrcdir/build/mozconfig.nasm"
. "$topsrcdir/build/mozconfig.node"
. "$topsrcdir/build/mozconfig.automation"
. "$topsrcdir/build/mozconfig.rust"
. "$topsrcdir/build/mozconfig.cache"