Bug 1574657: switch taskcluster provisionerId/workerType for community deployment

[milescrabill]

Hi!

I work on the Taskcluster team at Mozilla, and I'm writing to let you know about an upcoming change to our deployment of Taskcluster that will affect this project's use of Taskcluster for CI/CD.

We're splitting Taskcluster for Firefox CI and Taskcluster for community projects into separate deployments. The current integration will continue to work through November 9th, at which point this change will be needed for your Taskcluster integration to continue to work.

The first step of the conversion work happened here: https://github.com/mozilla/activity-stream/pull/5288, that PR upgraded the syntax of the taskcluster.yml file and Github integration to v1.

There are two next steps:

• changing the Github integration used by this project from Taskcluster to use community-tc-integration
• changing the provisionerId and workerType in your taskcluster.yml - I've done that for you in this PR.

After you swap the Github Integration over, merging this PR should get you in a good state. We have a bug tracking this work here.

Let me know if you have any questions or need guidance!

[milescrabill]

Note that the failure to submit the task to Taskcluster is because the integration hasn't been updated, the workerType and provisionerId changes are only scoped on the community deployment of Taskcluster. (so this is expected)

[milescrabill]

@piatra as the Taskcluster cutover date approaches we're trying to get things moved over. Aside from wanting to transition things to Windows, is there a blocker for this?

[milescrabill]

Thank you for iterating on this! Sorry it was such a pain. 😅