[JIRA] (JENKINS-13117) Allow triggering on the change-merged event too
David Pursehouse resolved JENKINS-13117 as Fixed Allow triggering on the change-merged event too This is implemented in the latest master. Several commits starting with this one: https://github.com/jenkinsci/gerrit-trigger-plugin/commit/f10925ee0b7725727b6e9a4a104016fe4619deac Change By: David Pursehouse (13/Jul/12 2:36 PM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-13117) Allow triggering on the change-merged event too
[
https://issues.jenkins-ci.org/browse/JENKINS-13117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160392#comment-160392
]
rsandell commented on JENKINS-13117:
https://github.com/jenkinsci/gerrit-trigger-plugin/pull/9
Allow triggering on the change-merged event too
---
Key: JENKINS-13117
URL: https://issues.jenkins-ci.org/browse/JENKINS-13117
Project: Jenkins
Issue Type: Improvement
Components: gerrit-trigger
Reporter: R. Tyler Croy
Assignee: rsandell
Gerrit will fire a {{change-merged}} event when a change is Submitted (i.e.
merged) into the destination branch.
It would be most useful to be able to allow a job to be triggered off of the
usual {{patchset-created}} event (existing behavior), as well as the
{{change-merged}} event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13117) Allow triggering on the change-merged event too
R. Tyler Croy created JENKINS-13117:
---
Summary: Allow triggering on the change-merged event too
Key: JENKINS-13117
URL: https://issues.jenkins-ci.org/browse/JENKINS-13117
Project: Jenkins
Issue Type: Improvement
Components: gerrit-trigger
Reporter: R. Tyler Croy
Assignee: rsandell
Gerrit will fire a {{change-merged}} event when a change is Submitted (i.e.
merged) into the destination branch.
It would be most useful to be able to allow a job to be triggered off of the
usual {{patchset-created}} event (existing behavior), as well as the
{{change-merged}} event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13117) Allow triggering on the change-merged event too
[
https://issues.jenkins-ci.org/browse/JENKINS-13117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160347#comment-160347
]
R. Tyler Croy commented on JENKINS-13117:
-
[Event
documentation|http://gerrit-documentation.googlecode.com/svn/Documentation/2.2.2/cmd-stream-events.html#_events]
Allow triggering on the change-merged event too
---
Key: JENKINS-13117
URL: https://issues.jenkins-ci.org/browse/JENKINS-13117
Project: Jenkins
Issue Type: Improvement
Components: gerrit-trigger
Reporter: R. Tyler Croy
Assignee: rsandell
Gerrit will fire a {{change-merged}} event when a change is Submitted (i.e.
merged) into the destination branch.
It would be most useful to be able to allow a job to be triggered off of the
usual {{patchset-created}} event (existing behavior), as well as the
{{change-merged}} event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
