1757486 - [meta] gecko nightly promotion

Status: NEW

(Release Engineering :: General, task)

Description

[Aki Sasaki (not active)]

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
• shippable builds phase 1
• shippable builds phase 2
• Callek's beetmover paths proposal
• 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

Comment 1

[Aki Sasaki (not active)]

Likely, the first step here is to revisit the previous planning and craft a project proposal. There are a number of breaking changes here, noted in the caveats section above, so we likely need to get approval from various other teams.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:eijebong, maybe it's time to close this bug?

Comment 3

[Bastien Orivel [:eijebong]]

Discussed in team meeting, worth keeping around even if it's not a priority