It would be great if i could add jobs via a preset dropdown. This would make it easier to kick of test runs for the debugger, other devtools panes, or any other set of tests organized via presets preset.

One usecase, is reviewing contributor patches quickly. At the moment, I need to pull down the patch and kick off a try run. Or manually select all of the jobs via treeherder. This could be a huge time saver.

CC Armen

Not clearing the NI.

jlast, can this wait for a bit before I dig deeper into what it is needed?

There are some performance issues on Treeherder I'm currently investigating.

Absolutely.

Does the new "Add new jobs (search)" dialog help at all? It isn't preset, but you can at least narrow things down with a filter.

Perhaps we could investigate storing some saved searches in localStorage? Or a deeper change would be to add these to the user's profile somehow.

Hmm, I definitely appreciate finding a creative solution. The advantage with presets is that we have spent quite a bit of time fine-tuning our preset to include just the right jobs and a simple search would be really hard to replicate that. Saved searches would work if they are shared for everyone so that anyone on the team could use it, but it could go out of sync with presets.

Thanks for your patience. From my analysis this is not trivial feature request and we will need some work in m-c.

ahal, I would like to have some consumable source (it coud be an artifact) that would contain what kind of tasks each preset contains or even an adr recipe. How do you see this could be solved?

I guess you could have a task that runs ./mach try --preset <preset> --no-push and then save the resulting try_task_config.json as an artifact. I'm not very confident this would be the best approach, but don't have any other ideas.

I'm not going to have much time to work on this further, but I touched up some work in progress stuff I had laying around to let the user save their selected jobs from the "Add New Jobs (Search)" dialog as presets that they can re-use later. The presets are saved in localStorage as lists of task labels, so they're specific to the user and are easy to accidentally blow away if you erase localStorage, but it might be something to build from. If there's a way to run the task mentioned in comment 8, maybe those presets could be hard-coded into the list of saved presets, but available to everyone?

We're looking to tackle this on Q4