autoland's `release_level` property should be `production`
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(Not tracked)
People
(Reporter: bhearsum, Unassigned)
Details
release-level is a bit of a weird property in taskgraph, mostly because historically it was only used to configure release promotion tasks. It can be either production or staging, which is controlled by whether or not the project is in RELEASE_PROJECTS. RELEASE_PROJECTS is ostensibly any production repository that we run release promotion from. (Note that this is different than RELEASE_PROMOTION_PROJECTS, which is the former + try and some other project branches.)
We commonly use release-level to decide whether to use L1 or L3 scriptworkers. This works fine for most things, but ever since https://bugzilla.mozilla.org/show_bug.cgi?id=1752111, we began running treescript tasks on autoland, and added a fairly hack block which uses L3 workers when release-level is staging for autoland. Seeing L3 workers being used inside of something called "staging" is a bit strange, and a cause for alarm if you don't understand why.
One thing we could do to fix this is to change how release-level is defined. Perhaps by always setting it to production for autoland, or perhaps by detaching it from RELEASE_PROJECTS altogether.
(We may also want to consider a more broad revamping of this and other properties - I suspect there's many other inconsistencies that have emerged over the years - but that's beyond the scope of this bug.)
Description
•