1078260 - Move main gecko_version definitions to external file

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Rail Aliiev [:rail]]

See http://hg.mozilla.org/build/buildbot-configs/file/b00b824aa3ba/mozilla/master_common.py#l246

It would be better to have those in an external JSON file so we can easily bump them programatically.

Assigning to myself for now.

Comment 1

[[e-mail] (:bhearsum)]

https://github.com/mozilla/build-tools/blob/master/buildfarm/maintenance/production-branches.json might be a good choice for now, assuming it's something we've actually maintained? It seems to be missing some branches that exist, and contain some that don't (eg, IonMonkey).

Comment 2

[[e-mail] (:bhearsum)]

One complication that I just realized here is that this file impacts things at buildbot master start/reconfig time -- which means we should require a reconfig when this file changes, and sourcing it from master_common.py. This is probably not a big deal, just a change in process.

Comment 3

[Rail Aliiev [:rail]]

Attachment: gecko_version-buildbot-configs.diff

Comment 4

[Rail Aliiev [:rail]]

Attachment: gecko_version-tools.diff

Comment 5

[Rail Aliiev [:rail]]

Comment on attachment 8513844 [details] [diff] [review]
gecko_version-tools.diff

https://hg.mozilla.org/build/tools/rev/d522f0f2cb78

Comment 6

[Rail Aliiev [:rail]]

Comment on attachment 8513843 [details] [diff] [review]
gecko_version-buildbot-configs.diff

https://hg.mozilla.org/build/buildbot-configs/rev/0400b51f41d2

Comment 7

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

In production: https://hg.mozilla.org/build/buildbot-configs/rev/0400b51f41d2