While |mach try fuzzy| is generally a better experience than try syntax, there are a few cases where it can be annoying. One common case was when you selected a bunch of tasks in the interface and pushed. Then at a later date you wanted to push the exact same set of tasks again. This used to be a really poor experience as you needed to re-select all the same tasks manually.
As of now, you can use |mach try again| instead. The general workflow is: $ ./mach try fuzzy <select tasks> ... <uh oh, something failed> <fix> $ ./mach try again *More Details* Whenever you push to try with a `try_task_config.json` (aka anything but try syntax), that config will be saved in a history file (in ~/.mozbuild/history/try_task_configs.json). You can view your history keyed by commit message by running: $ ./mach try again --list If you wish to re-push an older `try_task_config.json`, you can use: $ ./mach try again --index <num> Where <num> is the number displayed by --list. By default the last 10 pushes will be saved in history, but this can be configured by setting: [try] maxhistory=<num> in your ~/.mozbuild/machrc. *Caveats* As mentioned earlier, pushes with try syntax aren't saved in history as they don't use `try_task_config.json` files. When/if bug 1400295 lands, then pushes generated with try syntax will start working. The full taskgraph might change between the time you originally ran the push and the time you re-push with |mach try again|. If this happens, it's possible the tasks you previously scheduled were renamed (or removed) and the decision task will fail. -Andrew _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
