Closed Bug 1624280 Opened 5 years ago Closed 5 years ago

Allow specifying custom routes in `mach try fuzzy`

Categories

(Developer Infrastructure :: Try, enhancement)

enhancement
Not set
normal

Tracking

(firefox76 fixed)

RESOLVED FIXED
mozilla76
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.

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.

Assignee: nobody → james
Status: NEW → ASSIGNED

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.

Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/autoland/rev/16b40ed95ab6 Add support for routes in try_task_config.json, r=ahal https://hg.mozilla.org/integration/autoland/rev/a741a36b7d3f Allow specifying routes in mach try fuzzy, r=ahal
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: