Uplift remaining GCP worker config to esr102
Categories
(Release Engineering :: Firefox-CI Administration, task)
Tracking
(firefox-esr102 fixed)
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | fixed |
People
(Reporter: ahal, Assigned: ahal)
References
Details
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-esr102+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
Details | Review |
The ESR 102 branch forked before we could complete the migration work. This bug will track "uplifting" the remaining changes there.
I put "uplifting" in quotes because rather than try to actually rebase the dozens of patches that would be needed and dealing with conflicts, my plan is to simply modify taskcluster/ci/config.yml
such that all worker aliases are pointing at the GCP pools.
Assignee | ||
Comment 1•3 years ago
|
||
This is an "uplift" of the patches that have landed on central and made / are
making their way down to release.
By pointing all aliases to GCP pools, I can avoid rebasing dozens of commits
and dealing with the inevitable merge conflicts.
Assignee | ||
Comment 2•3 years ago
|
||
Comment on attachment 9308579 [details]
Bug 1805194 - [ci] Migrate tasks from AWS -> GCP, r?masterwayz!
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: We'd like to move everything out of AWS before esr102 is decommissioned.
- User impact if declined: None
- Fix Landed on Version:
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Not part of the build so low risk to users. May break release graphs, but we can switch any busted tasks back to AWS in the worst case scenario. Release tasks have been running in GCP on central / beta / release with minimal issues so it should be safe.
Comment 3•3 years ago
|
||
Comment on attachment 9308579 [details]
Bug 1805194 - [ci] Migrate tasks from AWS -> GCP, r?masterwayz!
Approved for ESR102.
Comment 4•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Comment 5•3 years ago
|
||
Comment 6•3 years ago
|
||
bugherder uplift |
Comment 7•3 years ago
|
||
bugherder uplift |
Description
•