Closed Bug 1384205 (comm-taskcluster) Opened 3 years ago Closed 1 year ago
[Tracker] Port comm-central to use taskcluster
Thunderbird needs to move off of RelEng's buildbot cluster. We are currently planning to move to taskcluster.
Severity: normal → blocker
Priority: -- → P1
Target Milestone: --- → Thunderbird 59.0
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? :-)
:emorley Thunderbird only uses buildbot on esr52 now.
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.)
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.