On Fri, May 26, 2017 at 06:20:33PM -0400, Dustin Mitchell wrote: > Andrew, I apologize for not giving credit -- the "try this" variant is > intended to be exactly what you've proposed in that blog entry. > > I like the idea of doing the processing client-side. I think we will > still want awareness of the three options in taskcluster/, though: > - "there is no try" is basically a normal push > - "try this" amounts to a simple target_task method (return > task.label in config.params['requested_tasks'] or something like that) > - "trying my patience" would be legacy, so re-implementing it > elsewhere is probably not productive. It could potentially feed into > the "try this" implementation. > I've copied you on more bugs than you probably want, and will continue > to do so :) > > Callek, I think this would be command-line accessible at any rate. > Whether it's accessible with a command line embedded in a commit > message is an open question, but certainly the trivial "I want to run > the task labeled foo-bar" will be a one-liner, either via mach, an hg > extension, or simple hg syntax.
Please make it so that it's possible to figure out why some job has run or not. Currently, it's near impossible. Case at point: I recently had two try pushes run a tc[tier2](l10n) job, that happens to be busted for reasons entirely unrelated to my changes, and I have no idea why it was triggered. It gets better: another try push of mine with about the same changes did *not* trigger it. Also, in multiple occasions, I've had to wonder why jobs have not been started that I was expecting to have. Mike _______________________________________________ dev-builds mailing list [email protected] https://lists.mozilla.org/listinfo/dev-builds
