[JIRA] (JENKINS-23873) extend changeMerged event with merge commit
Title: Message Title George Young closed an issue as Fixed I assume this has been tested so look forward to using this when we upgrade our Gerrit to v2.11 Jenkins / JENKINS-23873 extend changeMerged event with merge commit Change By: George Young Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more option
[JIRA] (JENKINS-23873) extend changeMerged event with merge commit
Title: Message Title George Young commented on JENKINS-23873 Re: extend changeMerged event with merge commit Looks like a commit by Jan Dohl achieves this result, found in plugin version gerrit-trigger-2.21.0 which creates the GERRIT_NEWREV Jenkins job variable when listening to Gerrit v2.11 streaming ref_updated or change_merged events with the new JSON field new_rev field Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-23873) extend changeMerged event with merge commit
George Young created JENKINS-23873 extend changeMerged event with merge commit Issue Type: 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 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-23873) extend changeMerged event with merge commit
George Young updated JENKINS-23873 extend changeMerged event with merge commit Change By: George Young (18/Jul/14 1:44 PM) Issue Type: Bug Improvement 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter] (JENKINS-21307) Hard coded rest API version should be parameterized
george dma created JENKINS-21307 Hard coded rest API version should be parameterized Issue Type: Bug Assignee: Unassigned Components: jiratestresultreporter Created: 09/Jan/14 2:47 PM Description: When using this plugin on an old version of JIRA like v4.4.4 the rest API url is http://localhost:8080/rest/api/2.0.alpha1/issue and not /rest/api/2/issue/. In the code I saw on line 151 String url = "" + "rest/api/2/issue/"; Please make it so that this string is parametrized so that we can define it ourselves due to different JIRA versions. Project: Jenkins Labels: plugin jira Priority: Major Reporter: george dma 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
