Move Thunderbird build jobs to GCP workers
Categories
(Thunderbird :: Build Config, task)
Tracking
(thunderbird_esr102 unaffected)
| Tracking | Status | |
|---|---|---|
| thunderbird_esr102 | --- | unaffected |
People
(Reporter: rjl, Assigned: rjl)
References
Details
Attachments
(2 files)
Most Firefox builds run on GCP workers rather than AWS now. It's time to do the same for Thunderbird build jobs.
Among other things, the GCP workers all have 64G of RAM, the AWS workers range from 32G-48G. This makes a difference during libxul linking; we have macOS debug builds that do not complete on the smaller AWS workers because they run out of memory.
Changes to worker-pools.yml in the ci-configuration repository need to be made first.
{pool-group}/b-linux-gcp, {pool-group}/b-linux-large-gcp, {pool-group}/b-linux-xlarge-gcp need to have the additional pool-group and max-capacity values added to them like the non-gcp equivalents of those pools (maybe more things too).
In comm-central, /comm/taskcluster/ci/build/* need to be updated to set worker-type: b-linux-gcp
(-large and -xlarge variants won't be used just yet, but I expect that toolchain jobs will be moving soon, and they will use those variants.)
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
|
|
Assignee | |
Comment 2•2 years ago
|
||
Depends on D158694
Pushed by jcristau@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/acb73757b046 Create b-linux-gcp pools for comm pool groups. r=releng-reviewers,jcristau
|
|
Assignee | |
Updated•2 years ago
|
Pushed by thunderbird@calypsoblue.org:
https://hg.mozilla.org/comm-central/rev/0f1f45ab43cb
Switch CI builds to GCP workers. r=dandarnell
|
||
Updated•1 year ago
|
|
|
Assignee | |
Comment 5•1 year ago
|
||
For the record, c-esr102 will be covered by an esr102-specific patch in bug 1798529.
Description
•