Closed Bug 1384205 (comm-taskcluster) Opened 3 years ago Closed 1 year ago

[Tracker] Port comm-central to use taskcluster.

Categories

(Thunderbird :: Build Config, enhancement, P1, blocker)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED
Thunderbird 59.0

People

(Reporter: tomprince, Assigned: tomprince)

References

(Depends on 2 open bugs)

Details

(Keywords: meta)

Thunderbird needs to move off of RelEng's buildbot cluster.

We are currently planning to move to taskcluster.
Depends on: 1384210
Depends on: 1384273
Depends on: 1384319
Depends on: comm-taskgraph
Depends on: 1385055
Depends on: 1385094
Blocks: 1380171
Depends on: 1406987
Depends on: 1408145
Depends on: 1408574
Depends on: 1408579
Depends on: 1410118
Depends on: 1410133
Depends on: 1410203
Depends on: 1410512
Depends on: 1410519
Depends on: 1410737
Depends on: 1410773
Depends on: 1412354
Depends on: 1413976
Depends on: 1410513
Depends on: 1416029
Depends on: 1417319
Depends on: 1418058
Depends on: 1418593
Duplicate of this bug: tb-taskcluster
Severity: normal → blocker
Priority: -- → P1
Target Milestone: --- → Thunderbird 59.0
Blocks: ccrework, 1222693
Status: NEW → ASSIGNED
Keywords: meta
Depends on: 1418654
Depends on: 1418882
Depends on: 1418883
Depends on: 1419141
Depends on: 1419464
Depends on: 1419474
Depends on: 1419582
Depends on: 1421002
Depends on: 1421062
Depends on: 1421466
Depends on: 1422046
Depends on: 1424146
Depends on: 1424171
Depends on: 1425131
Depends on: 1425148
Depends on: 1425194
Depends on: 1425931
Depends on: 1426209
Depends on: 1430661
Depends on: 1430823
Depends on: 1431269
Depends on: 1434365
Depends on: 1439254
Depends on: 1439258
Depends on: 1439265
Depends on: 1439469
Depends on: 1442851
Blocks: 1443251
Depends on: 1447436
Depends on: 1447460
Depends on: 1451968
Depends on: 1452150
Depends on: 1453885
Depends on: 1455407
Depends on: 1455757
Depends on: comm-relpro
Depends on: 1460320
Depends on: 1461392
Depends on: 1461716
Depends on: 1464523
Depends on: 1464530
Depends on: 1467266
Depends on: 1475868
Hi! ESR 52 had it's last official release on 2018-06-26, and once this release cycle comes to an end (ESR 60.2 is due for release on 2018-09-05), ESR 52 will be officially EOL. At that point, the comm-central related repositories will be the last to be using buildbot. The Treeherder team are keen to remove buildbot data ingestion support as soon as possible after that date, since it will allow us to simplify quite a lot of our data ingestion layer and alleviate a fair bit of technical debt (and I'm guessing similar applies to other teams too).

I can see some heroic work has been going on in the many many dependants of this bug, and was curious as to whether you had a rough estimate for when the transition might be complete? :-)
Flags: needinfo?(mozilla)
:emorley Thunderbird only uses buildbot on esr52 now.
Flags: needinfo?(mozilla)
I think the only thing that would block killing comm-esr52 infra is discovering some catastrophic issue that would prevent us from globally releasing version 60 in the next 1-2 months. There is not yet an solid answer to that scenario, because we have not released 60.
Ah great! It sounds like the timelines will align well with the EOL of Firefox ESR52. (I didn't realise the open dependant bugs here are for nice-to-have follow-ups, rather than remaining work relating to moving non-ESR-52 repos away from buildbot.)
No longer blocks: 1443251
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.