Migrate bugbug to community taskcluster deployment
Categories
(Taskcluster :: Operations and Service Requests, task)
Tracking
(Not tracked)
People
(Reporter: dustin, Assigned: bstack)
References
Details
bugbug uses TC for its CI. It also has some hooks and indexes some tasks.
I'll have a closer look regarding
- how the hooks are configured and how to do that in the new deployment of TC
- how index URLs are generated and used and how to use a new rootUrl
- any necessary updates to CI
Reporter | ||
Comment 1•5 years ago
|
||
(notes to myself)
.taskcluster.yml
is already v1 🎉. This will just need the usual provisionerId/workerType changes when it migrates- tag pushes upload docker images using task-boot and secret project/relman/bugbug/deploy
- tag pushes create hooks using task-boot
- data pipeline hook update ends with a message to route
project.relman.bugbug.deploy_ending
; the pipeline hook listens for this
So it looks like the long pole here will be updating task-boot to handle a new rootUrl (so, mostly, updating the version of the TC client it uses).
Reporter | ||
Comment 2•5 years ago
|
||
(and that pole's not very long)
Reporter | ||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Notes to self:
- They have custom workerType: relman-svc
Comment 4•5 years ago
|
||
(In reply to [:owlish] from comment #3)
Notes to self:
- They have custom workerType: relman-svc
And relman-svc-compute
Reporter | ||
Comment 5•5 years ago
|
||
PSA: The existing (https://taskcluster.net) deployment will be shut down a week from today, on November 9. After that point, any CI not migrated to the new community cluster will stop functioning. The TC team is ready and eager to help get everything migrated by that time, but the deadline is firm.
Apologies for failing to communicate this as broadly and loudly as necessary, and for the bugspam now.
Assignee | ||
Updated•5 years ago
|
Comment 6•5 years ago
|
||
Description
•