1574905 - Migrate one-off-system-add-ons to community taskcluster deployment

Status: RESOLVED FIXED

(Taskcluster :: Operations and Service Requests, task)

Description

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

Make a plan to move this project to the new community deployment.

This project just runs lint on pushes.

Comment 1

[Robert Helmer [:rhelmer]]

CC:'ing Rehan who is working on moving add-ons that we use for roll-out and hotfixes to Normandy. It might make sense to archive the "one-offs" repo at some point and move to something new, Rehan wdyt?

Comment 2

[Rehan Dalal (Inactive)]

It would be ideal to move off of the mono repo and have individual repos for every addon in the future

Comment 3

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

Does it makes sense to sunset the existing one-offs repo when we shut down the current Taskcluster deployment (~early November), and start fresh with this on the new Taskcluster deployment (ready in October, maybe earlier)?

Comment 4

[Robert Helmer [:rhelmer]]

(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #3)

Does it makes sense to sunset the existing one-offs repo when we shut down the current Taskcluster deployment (~early November), and start fresh with this on the new Taskcluster deployment (ready in October, maybe earlier)?

Hm, well one complication is that (as of armag-add-on 2.0) we're re-considering exactly how far back to support Firefox releases, and current ESR-1 seems to be the consensus. So we'll need to keep a way to do this for a while at least.

However it doesn't need to be this repo and should probably be the new setup Rehan is working on. So, yes? :)

Comment 5

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

OK, sounds good. I'll let you know when the new community deployment is ready, and we can figure out where things are at then.

Comment 6

[Miles Crabill [:miles]]

Hey folks, the community deployment is ready, so we're back with questions about this repo [0]. To get this working with the community deployment we would update the .taskcluster.yml to support v1 of the Taskcluster Github integration [1], swap out the provisioner and worker type, and would need to switch out your Github Integration to the community integration [2].

Has the new way forward for this repo / individual addon repos been decided? Do you want me to make the above steps to get CI in place for this repo in the community deployment of Taskcluster?

[0] https://github.com/mozilla/one-off-system-add-ons
[1] https://docs.taskcluster.net/docs/reference/integrations/github/taskcluster-yml-v1
[2] https://github.com/apps/community-tc-integration/

Comment 7

[Rehan Dalal (Inactive)]

302-ing to aki

Comment 8

[Aki Sasaki (not active)]

I'm working on CoT-enabled taskcluster automation for addons. We will likely be moving these to the Firefox cluster.