Migrate task-boot to community taskcluster deployment
Categories
(Taskcluster :: Operations and Service Requests, task)
Tracking
(Not tracked)
People
(Reporter: dustin, Assigned: bstack)
References
Details
Make a plan to move this project to the new community deployment.
Reporter | ||
Comment 1•5 years ago
|
||
Bastien, I see that one of the three tasks defined in .taskcluster.yml
runs on the releng-svc
worker, while the rest run on generic-worker. Is that an important distinction, or just one of convenience?
Comment 2•5 years ago
|
||
I use releng-svc
only to get the privileged: true
capability, as this is needed to build the docker image through img
.
If you can give me access to a worker with that capability on the new deployment, we can easily update the .taskcluster.yml
.
Updated•5 years ago
|
Reporter | ||
Comment 3•5 years ago
|
||
Thanks for the update! The current rough plan is to have per-project workers, so you can have all the privileged and unprivileged workers you want :)
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 4•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.
Comment 5•5 years ago
|
||
Could you enable the new Taskcluster Github app on https://github.com/mozilla/task-boot and create a new provisionner proj-taskboot
?
I'll then make a PR to use that provisionner and ci
workerType.
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Done! Thanks :bstack!
Description
•