|
||||||||
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-15313) Trigger on Updated Chang... gbouge...@gmail.com (JIRA)
- [JIRA] (JENKINS-15313) Trigger on Updated ... rsand...@java.net (JIRA)
- [JIRA] (JENKINS-15313) Trigger on Updated ... gbouge...@gmail.com (JIRA)
- [JIRA] (JENKINS-15313) Trigger on Updated ... rsand...@java.net (JIRA)
- [JIRA] (JENKINS-15313) Trigger on Updated ... gbouge...@gmail.com (JIRA)
- [JIRA] (JENKINS-15313) Trigger on Updated ... gbouge...@gmail.com (JIRA)
The refUpdated event that gerrit sends does not contain a ref spec, since it is not tied to a change. So there is no parameter added to the build named GERRIT_REFSPEC when it is triggered bu a ref updated event.
This makes it hard to easily configure a job to trigger on both "change based" events and ref updated events. unless you use a bash script or something to check out the code.
I missed to add that to the help text.