1562222 - [project-migrations] Build a new TC deployment for non-Firefox projects

Status: RESOLVED FIXED

(Taskcluster :: Operations and Service Requests, task)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

The TC team will need a deployment for its own CI, and can probably share that with a lot of the other projects that will not be moved to the Firefox CI deployment (most of which are using GitHub).

This bug tracks:

• planning and setting up that deployment
• migrating projects to it

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

Attachment: builds.txt

Attached is a list of all github repos that tc-github has built for, with the most recent date they were built. This should be a starting point to figuring out what needs to move.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

Coop is going to take a pass over that file and determine

• who is responsible
• whether they are actively using TC and need to be migrated to the new deployment

Just to drop the idea here, we could consider taking the opportunity of this interruption to:

• upgrade v0 .taskcluster.yml's to v1
• switch everyone to checks (??!!??)
  /cc owlish for thoughts on that topic.

Comment 3

[Chris Cooper [:coop] (he/him)]

I've dropped the project owner breakdown into the Google drive. Passing this back to Dustin.

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

https://docs.google.com/spreadsheets/d/17PTGXtpB-Au7qHk9b7FENEr71OSbBDggRBGsYSsoRE4/edit#gid=2079982348

Comment 5

[Simon Sapin (:SimonSapin)]

Re comment 4, WebRender and Servo should likely be considered two separate projects.

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

All that remains here is the migrations to this new cluster. It was a weird way to set up a dependency tree -- sorry about that -- but it will be gone in a week.