Allow specifying custom routes in `mach try fuzzy`
Categories
(Developer Infrastructure :: Try, enhancement)
Tracking
(firefox76 fixed)
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: jgraham, Assigned: jgraham)
Details
Attachments
(2 files)
This is useful for tools that want to listen for task completion using the notify.*.on-*
routes; by adding a tool-specific notification key you can listen to e.g. pulse messages just for tasks that you scheduled rather than having to sift through ~everything.
It's somewhat unclear if the mechanism should be "allow specifying any additional route" or something more specific to the usecase. With unfettered access to the routes, one could potentially do something broken or confusing.
Assignee | ||
Comment 1•5 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&selectedJob=294321419&revision=0620cfba9b942f2b7e2ced4d75ecd3525da75424 is a try push with this working.
Assignee | ||
Comment 2•5 years ago
|
||
This adds an optional routes key to the task_task_config schema,
which is a list of strings. Anything in this key is added to the list
of routes for tasks scheduled by the decision task.
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
These routes are applied to all tasks except the decision task. There
is currently no validity checking in the frontend, so if the provided
routes aren't valid the decision task will fail.
Comment 5•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/16b40ed95ab6
https://hg.mozilla.org/mozilla-central/rev/a741a36b7d3f
Updated•2 years ago
|
Description
•