1535635 - disable mozilla-taskcluster and remove temporary changes from ci-admin/configuration

Status: RESOLVED FIXED

(Taskcluster :: Services, defect)

Description

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

I've used feature.taskcluster-push-via-hooks to identify projects that are using hooks for pushes, so that mozilla-taskcluster would ignore them. Once mozilla-taskcluster is disabled (in a roll-backable way), I can revert this to just feature.taskcluster-push.

Comment 1

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

https://github.com/taskcluster/mozilla-taskcluster/pull/139

Comment 2

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

I just deleted all of mozilla-taskcluster's scopes:
https://tools.taskcluster.net/auth/clients/project%2Ftaskcluster%2Fmozilla-taskcluster%2Fproduction-3

which should prevent it from spuriously starting any tasks.

Comment 3

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

I also scaled it down to zero dynos (pushlog, worker, and pulse_listener). If we roll back, we'll want to scale pushlog and worker back up to 1 and wait for them to come up-to-date with all repos.

Comment 4

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

PR landed and deployed.

Comment 5

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

Attachment: Bug 1535635 - use feature.taskcluster.push to enable hg pushes

Comment 6

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

Attachment: Bug 1535635 - make features.taskcluster-push enable hg-pushes; r=tomprince