On Wed, Oct 23, 2013 at 1:25 AM, Thomas Broyer <[email protected]> wrote:
> You might want to add those instructions to the README file, for anyone > willing to hack on them. > https://gwt-review.googlesource.com/#/c/5080/ (one issue with the current code, unless you fixed it recently, is that > it'll post Verified+1 / Verified-1 for old patchsets, in the event that you > posted a new patchset when the new one was being built – or queued; also, I > haven't checked, but it'd be great to cancel builds for patchsets that are > now obsolete, either cancelling them if they're queued or just making them > no-ops when they'll run) > Yep, that's certainly an issue. The current jenkins interface is pretty minimal, just enough to fire off additional presubmit jobs (jenkins.go<https://gwt.googlesource.com/buildglue/+/86b6e7e3c9e209436f096301a5b251dbe3de5edf/jenkins/jenkins.go>). I imagine it wouldn't be hard to add some additional methods for checking what presubmit jobs are pending and cancelling a pending job. Filed https://code.google.com/p/google-web-toolkit/issues/detail?id=8406 to keep track of it. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
