No obvious way to tell what a mach try preset really maps to
Categories
(Developer Infrastructure :: Try, enhancement)
Tracking
(Not tracked)
People
(Reporter: bzbarsky, Unassigned)
References
Details
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Comment 1•7 years ago
|
||
Updated•7 years ago
|
Updated•6 years ago
|
Comment 2•6 years ago
|
||
With the landing of bug 1518572, I think this bug can be closed. Presets are now more structured and look like this:
<name>:
selector: <selector>
<args>
So for example, saving a preset like this:
$ ./mach try fuzzy --save foo --query "linux64 debug mochitest"
Will result in a preset like this:
foo:
selector: fuzzy
query:
- "linux64 debug mochitest"
The <args> portion of a preset directly corresponds to the parameters each selector's run function takes. In fuzzy's case, that is this function:
https://searchfox.org/mozilla-central/source/tools/tryselect/selectors/fuzzy.py#207
Also preset names from different selectors can no longer collide.
Boris, please feel free to re-open if you think there are still things to fix here.
Reporter | ||
Comment 3•6 years ago
|
||
No, I think this does what I wanted, in terms of being able to figure out what a preset does. The syntax ones are listed in a kinda annoying way that makes it hard to edit them to create a new one, but I can manage. ;)
Updated•2 years ago
|
Description
•