Now that releng are no longer using it (bug 1259627) we should be able to remove all traces of it.
Things I can think of: * remove scheduler/schedulerevents from https://references.taskcluster.net/manifest.json (done) * regenerate all clients * remove all scopes that refer to scheduler from roles/clients * update github repo to say it is no longer in service * update doc references, in our schemas/references, in the docs site, and in anything that uploads docs * terminate heroku dynos * delete/release any persistent storage the service used * delete heroku app * send out communication about sunset * close all open issues/PRs/bugzilla bugs related to scheduler * mark bugzilla component as obsolete so no new bugs land there * sing songs by candlelight to commemorate our sunken hero * check nothing in tools.taskcluster.net hits any scheduler endpoint I no doubt missed other things, pitch in if you think of something!
This is now the only open bug in Taskcluster :: Scheduler - I've closed/moved all the others.
(In reply to Pete Moore [:pmoore][:pete] from comment #1) > * remove all scopes that refer to scheduler from roles/clients I found these in the Scope Inspector (https://tools.taskcluster.net/auth/scopes/): scheduler:* scheduler:create-task-graph scheduler:extend-task-graph scheduler:extend-task-graph:* scheduler:route:gaia-taskcluster scheduler:route:taskcluster-github.*
Commit pushed to master at https://github.com/taskcluster/taskcluster-client-java https://github.com/taskcluster/taskcluster-client-java/commit/13d3b6368ae8a4bb3c5d9cffe2fa092e1a9d7333 Bug 1399437 - don't generate scheduler classes
Removed scheduler from taskcluster-client-go and taskcluster-client-java
(In reply to Pete Moore [:pmoore][:pete] from comment #5) > Removed scheduler from taskcluster-client-go and taskcluster-client-java Also updated github pages: * http://taskcluster.github.io/taskcluster-client-go * http://taskcluster.github.io/taskcluster-client-java