Close! There are a few exchanges that the queue publishes on, for different events in the lifetime of a task. task-defined, task-pending, task-running, etc. In fact, we don't translate task-defined into anything for treeherder. Events on each of those exchanges are handled in specific callbacks after line 287. As a note, the exchanges do not have a trailling `.#` on them -- I suspect you're confusing exchanges with routing key patterns (which do often have a trailing `.#`). Also, just to be clear, shutting down taskcluster-treeherder will mean that we no longer publish on exchange/taskcluster-treeherder/v1/jobs.
Bug 1395254 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Close! There are a few exchanges that the queue publishes on, for different events in the lifetime of a task. task-defined, task-pending, task-running, etc. In fact, we don't translate task-defined into anything for treeherder. Events on each of those exchanges are handled in specific callbacks after line 287. As a note, the exchanges do not have a trailling `.#` on them -- I suspect you're confusing exchanges with routing key patterns (which do often have a trailing `.#`). Also, just to be clear, shutting down taskcluster-treeherder will mean that we no longer publish on `exchange/taskcluster-treeherder/v1/jobs`.