Migrate redo to community taskcluster deployment
Categories
(Taskcluster :: Operations and Service Requests, task)
Tracking
(Not tracked)
People
(Reporter: dustin, Assigned: hassan)
References
Details
Make a plan to move this project to the new community deployment.
Reporter | ||
Comment 1•5 years ago
|
||
This will just need its provisionerId/workerType updated. I'll make a PR when we know what those are.
Reporter | ||
Comment 2•5 years ago
|
||
(confirmed, already a v1 .taskcluster.yml)
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Comment 4•5 years ago
|
||
Once comment 3 is merged & applied, the remaining TODOs are:
- Update
taskcluster.yml
to use the new provisionerId & workerType - Change the GitHub integration from Taskcluster to using https://github.com/apps/community-tc-integration
Reporter | ||
Comment 5•5 years ago
|
||
Agreed! We had a meeting today to work through the details of this stuff, and bstack will be scheduling more -- feel free to drop by to ask questions or get advice, since we're all working through this new stuff together..
Assignee | ||
Comment 6•5 years ago
|
||
Reporter | ||
Comment 7•5 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #5)
Agreed! We had a meeting today to work through the details of this stuff, and bstack will be scheduling more -- feel free to drop by to ask questions or get advice, since we're all working through this new stuff together..
That was the wrong bug, sorry!
Reporter | ||
Updated•5 years ago
|
Description
•