![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
rsandell
|
|
Components:
|
gerrit-trigger-plugin |
|
Created:
|
08/Dec/14 7:57 PM
|
|
Description:
|
When using JJB (Jenkins Job Builder) to create a Gerrit Trigger based job to trigger on a regex pattern in the comment field. The jobs will fail to trigger if created in this way.
I know of 2 workarounds:
1. Navigate to the job configure page and hit save
2. Restart Jenkins process
Notice that if workaround 1 is used the new config.xml created will be identical to the version of itself before save was clicked.
My guess is Gerrit Trigger code must be holding something that needs to be updated before it register's the Job's regex trigger. Saving and/or reloading Jenkins causes the update.
The JJB code for adding RegEx triggers can be found on OpenStack Gerrit at (at time of this writing it's not yet merged into JJB):
https://review.openstack.org/#/c/136605/
Any insight on this would be appreciated as the workarounds to move forward are not ideal.
|
|
Environment:
|
Jenkins with Gerrit Trigger plugin
Jenkins Job Builder for job management
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Thanh Ha
|
|
|
|
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.
