![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
rsandell
|
|
Components:
|
gerrit-trigger |
|
Created:
|
18/Jul/14 1:44 PM
|
|
Description:
|
as found here:
https://bugs.launchpad.net/openstack-ci/+bug/929723
and
http://code.google.com/p/gerrit/issues/detail?id=2785
The changeMerged event provides the merged patchset information of a review/change that was merged to its destination branch.
Can this event be extended, or a new event created to include the SHA of the merge commit that was written/exists on the destination branch so that an event listener, like the Jenkins Gerrit Trigger Plugin, could fetch the specified branch and rewind to the specific SHA for a per-review-on-the-branch build trigger?
The refUpdated event has essentially a rev-list of individual commits with no indication of which were added as a result of review merge
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
George Young
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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/d/optout.
