Despite this project existing in idea form for a number of years, I can't find a tracking bug, so filing this one. Essentially: Firefox Desktop nightlies use a different taskgraph code path and automation workflow than betas, releases, or ESRs. If we can use release automation in Nightlies, we then we can: - remove nightly-specific configurations and code for more maintainability, - add a shared bit of automation once rather than twice, - get up to an extra 4 weeks of testing for any release automation changes that land in central and ride the trains, resulting in more stable beta 1's - have the option of moving to ship-it nightlies Links: - [nightly release convergence doc](https://docs.google.com/document/d/1e9Uyq_N3m0Gzx4ut4GTatUyPKOZ-OASll9BhK_7LH1o/edit#) - [shippable builds phase 1](https://bugzilla.mozilla.org/show_bug.cgi?id=1352113) - [shippable builds phase 2](https://bugzilla.mozilla.org/show_bug.cgi?id=1614970) Caveats: - archive.m.o links and behaviors may change - nightlies currently allow for shipping platforms + locales as they finish, and releases restrict us to ship the entire release as a single transaction, blocking on broken platforms or locales
Bug 1757486 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Despite this project existing in idea form for a number of years, I can't find a tracking bug, so filing this one. Essentially: Firefox Desktop nightlies use a different taskgraph code path and automation workflow than betas, releases, or ESRs. If we can use release automation in Nightlies, we then we can: - remove nightly-specific configurations and code for more maintainability, - add a shared bit of automation once rather than twice, - get up to an extra 4 weeks of testing for any release automation changes that land in central and ride the trains, resulting in more stable beta 1's - have the option of moving to ship-it nightlies Links: - [nightly release convergence doc](https://docs.google.com/document/d/1e9Uyq_N3m0Gzx4ut4GTatUyPKOZ-OASll9BhK_7LH1o/edit#) - [shippable builds phase 1](https://bugzilla.mozilla.org/show_bug.cgi?id=1352113) - [shippable builds phase 2](https://bugzilla.mozilla.org/show_bug.cgi?id=1614970) - Callek's [beetmover paths proposal](https://github.com/Callek/beetmover-nightly-promotion) Caveats: - archive.m.o links and behaviors may change - nightlies currently allow for shipping platforms + locales as they finish, and releases restrict us to ship the entire release as a single transaction, blocking on broken platforms or locales
Despite this project existing in idea form for a number of years, I can't find a tracking bug, so filing this one. Essentially: Firefox Desktop nightlies use a different taskgraph code path and automation workflow than betas, releases, or ESRs. If we can use release automation in Nightlies, we then we can: - remove nightly-specific configurations and code for more maintainability, - add a shared bit of automation once rather than twice, - get up to an extra 4 weeks of testing for any release automation changes that land in central and ride the trains, resulting in more stable beta 1's - have the option of moving to ship-it nightlies Links: - [nightly release convergence gdoc](https://docs.google.com/document/d/1e9Uyq_N3m0Gzx4ut4GTatUyPKOZ-OASll9BhK_7LH1o/edit#) - [shippable builds phase 1](https://bugzilla.mozilla.org/show_bug.cgi?id=1352113) - [shippable builds phase 2](https://bugzilla.mozilla.org/show_bug.cgi?id=1614970) - Callek's [beetmover paths proposal](https://github.com/Callek/beetmover-nightly-promotion) - [RELENG-19](https://mozilla-hub.atlassian.net/browse/RELENG-19) Caveats: - archive.m.o links and behaviors may change - nightlies currently allow for shipping platforms + locales as they finish, and releases restrict us to ship the entire release as a single transaction, blocking on broken platforms or locales