https://bugzilla.wikimedia.org/show_bug.cgi?id=64015
Antoine "hashar" Musso <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|Unprioritized |Normal Status|PATCH_TO_REVIEW |ASSIGNED Assignee|[email protected]. |[email protected] |org | Severity|normal |enhancement --- Comment #2 from Antoine "hashar" Musso <[email protected]> --- Posted on qa-l http://lists.wikimedia.org/pipermail/qa/2014-April/001381.html the following: TL;DR: make 'recheck' by a whitelisted user to triggers tests jobs Gerrit/Zuul have a hidden feature which is that one can comment 'recheck' on a change in Gerrit and that reenqueue the Change in the Zuul 'check' pipeline. That pipeline is meant to run linting checks which are fast whereas the actual tests are run in a 'test' pipeline. From time to time people are using 'recheck' and wondering why only the lint jobs are being run. I have upgraded Zuul today and we can slightly enhance the way changes are added to pipelines. My proposal would be to have 'recheck' to trigger the test jobs, ie the one in the 'test' pipeline. The drawback is that non whitelisted user would no more be able to use it but I dont think it provided any added value. That would save people from having to create a new patchset (via rebase, or commit summary editing) and should save a bunch of time overall. Similarly, we could add a 'regate' comment that would enqueue the change if it has been already voted CR+2. Letting anyone resubmit a change without having CR+2 rights. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
