Migrate `release-{eme-free|partner}-repack-repackage` tasks to GCP
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(firefox-esr102 unaffected, firefox110 fixed, firefox111 fixed, firefox112 fixed)
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox110 | --- | fixed |
firefox111 | --- | fixed |
firefox112 | --- | fixed |
People
(Reporter: ahal, Assigned: ahal)
Details
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
dmeehan
:
approval-mozilla-beta+
jcristau
:
approval-mozilla-release+
jcristau
:
approval-mozilla-esr102-
|
Details | Review |
These tasks slipped through the cracks as the worker type was set in transform and we simply missed it in the huge amount of tasks being switched over.
Assignee | ||
Comment 1•1 year ago
|
||
These tasks slipped through the cracks.
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Comment on attachment 9317542 [details]
Bug 1816598 - [ci] Migrate 'release-{eme-free|partner}-repack-{beetmover|repackage}' tasks to GCP
Beta/Release Uplift Approval Request
- User impact if declined: We will be unable to release Firefox.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: Yes
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): NPOTB
- String changes made/needed:
- Is Android affected?: Yes
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration:
- User impact if declined: We will be unable to release Firefox.
- Fix Landed on Version:
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): NPOTB
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5d10831b7600 [ci] Migrate 'release-{eme-free|partner}-repack-{beetmover|repackage}' tasks to GCP r=releng-reviewers,hneiva
Comment 4•1 year ago
|
||
bugherder uplift |
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Comment on attachment 9317542 [details]
Bug 1816598 - [ci] Migrate 'release-{eme-free|partner}-repack-{beetmover|repackage}' tasks to GCP
esr102 doesn't need this, we moved things to gcp en-masse with https://hg.mozilla.org/releases/mozilla-esr102/rev/e42f4eb7c42678dfe72318ad3e95d57cd9efac0a and this was included.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Noticed in Comment 2, that Manual QA is needed for verifying this. Can you please help us with some steps, if that's the case?
Comment 7•1 year ago
|
||
bugherder |
Comment 8•1 year ago
|
||
We managed to perform a spot check on Windows 10x64 and macOS 1015, by using the EME-free builds. No issues were encountered.
Assignee | ||
Comment 9•1 year ago
•
|
||
(In reply to Julien Cristau [:jcristau] from comment #5)
Comment on attachment 9317542 [details]
Bug 1816598 - [ci] Migrate 'release-{eme-free|partner}-repack-{beetmover|repackage}' tasks to GCPesr102 doesn't need this, we moved things to gcp en-masse with https://hg.mozilla.org/releases/mozilla-esr102/rev/e42f4eb7c42678dfe72318ad3e95d57cd9efac0a and this was included.
Oh right, good catch :). I guess we had some confidence that it worked at least.
Sorry Mihai, it was late and I think I might have left the default value in. Not sure QA was needed, but still doesn't hurt to check. Thanks!
Comment 10•1 year ago
|
||
Comment on attachment 9317542 [details]
Bug 1816598 - [ci] Migrate 'release-{eme-free|partner}-repack-{beetmover|repackage}' tasks to GCP
Approved for 111.0b1.
Comment 11•1 year ago
|
||
bugherder uplift |
Description
•