gecko-dev/build/mozconfig.common.override
Mike Hommey 9961a0af3d 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: https://phabricator.services.mozilla.com/D21315

--HG--
extra : moz-landing-system : lando
2019-03-06 22:48:05 +00:00

16 lines
577 B
Plaintext

# 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 http://mozilla.org/MPL/2.0/.
# Common mozconfig for all users
#
# Add options to this file that will be inherited by all in-tree mozconfigs.
# This file is included at the *end* of the mozconfigs, and so may be used
# to override anything done previously.
#
# The common expected usage is for try builds with nondefault options.
if test -n "$USE_ARTIFACT"; then
. "$topsrcdir/build/mozconfig.artifact"
fi