| Summary: | user can start builds from a patch set on a review | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Sam Davis <sam.davis> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | Keywords: | helpwanted |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Sam Davis
+1. It's annoying but the only way I've figured out how to do this currently is by submitting a "fake" change. I was referring to builds that don't have a gerrit trigger and need to be started manually. It would be nice to be able to retrigger gerrit builds as well; the Hudson connector may already support that, I'm not sure. (In reply to comment #1) > +1. It's annoying but the only way I've figured out how to do this currently is > by submitting a "fake" change. You can retrigger builds from the Hudson web UI (if you are logged in). The Hudson connector does not support that though since it's an action that contributed by the Gerrit trigger plug-in.s Since the connector supports starting parameterized builds, it actually might not be hard to do this. An ambitious contributor could probably look at the Mylyn Builds UI plugin and port this functionality for use in the Mylyn Gerrit connector. A problem with this idea is that the parameter may not be called GERRIT_REFSPEC. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |