419687 - need a better way to manage tryserver mozconfigs

Status: RESOLVED INCOMPLETE

(Release Engineering :: General, defect, P3)

Description

[[e-mail] (:bhearsum)]

The try server mozconfigs are greatly out of sync with the nightly ones. We should manage these in a better way. We cannot simply use the nightly configs as the try servers contain extra things, most notably RUN_AUTOCONF_LOCALLY=1. One way to do this would be to use the tryserver mozconfigs as a place to store additions to the nightly one. At build time, Buildbot would merge the nightly, tryserver, and (possibly) user uploaded mozconfig.

Comment 1

[Robert Helmer [:rhelmer]]

(In reply to comment #0)
> The try server mozconfigs are greatly out of sync with the nightly ones. We
> should manage these in a better way. We cannot simply use the nightly configs
> as the try servers contain extra things, most notably RUN_AUTOCONF_LOCALLY=1.
> One way to do this would be to use the tryserver mozconfigs as a place to store
> additions to the nightly one. At build time, Buildbot would merge the nightly,
> tryserver, and (possibly) user uploaded mozconfig.
> 

If not, how about doing an include in the try-specific mozconfig e.g.:

. tinderbox-configs/nightly/linux/mozconfig
RUN_AUTOCONF_LOCALLY=1
# other try-specific stuff

You could also override any undesirable settings in this way, I think..

Comment 2

[[e-mail] (:bhearsum)]

That's certainly the easiest, and probably the preferably way to do it. I totally forgot that we could do that, heh.

Comment 3

[Philipp Kewisch [:Fallen][📱📆]]

This might also allow changing MOZ_CO_PROJECT, to allow for other apps?

Comment 4

[[e-mail] (:bhearsum)]

Mass change of target milestone.

Comment 5

[(not currently active) Ted Mielczarek]

This should be less of a problem on the mercurial builds, since there's no MOZ_CO_PROJECT, and RUN_AUTOCONF_LOCALLY is the default, but I guess we still have to support CVS builds for a while.

Comment 6

[[e-mail] (:bhearsum)]

I'm going to close this. If we want to clean up our mozconfigs in general, that's a larger bug.

Comment 7

[Chris Cooper [:coop] (he/him)]

Moving closed Future bugs into Release Engineering in preparation for removing the Future component.