Create `ship_firefox_partner_attribution` flavor for release promotion
Categories
(Release Engineering :: Release Automation, enhancement)
Tracking
(Not tracked)
People
(Reporter: jlorenzo, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
As of this writing, we only have one flavor when it comes to partner-attributed builds: promote_firefox_partner_attribution.
In order to be served through bedrock, we need some bouncer URLs. This means we need partner builds to be served under https://archive.mozilla.org/pub/firefox/releases/partners/ and bouncer aliases to be created and up to date. I don't believe these tasks should be moved to the promote phase. Instead, having a ship flavor looks saner.
Like in bug 1943598, we may have to split some existing tasks so they're targeted by this new flavor.
|
||
Comment 1•1 year ago
|
||
Like in bug 1943598, we may have to split some existing tasks so they're targeted by this new flavor.
Which tasks are you thinking of specifically?
|
Reporter | |
Comment 2•1 year ago
|
||
I'm thinking of release-beetmover-push-to-release andrelease-bouncer-aliases. This way, we don't affect the artifacts and alias entries that are not part of the partner distribution.
Description
•