|
||||||||
|
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-15214) Triggered build correct... [email protected] (JIRA)
- [JIRA] (JENKINS-15214) Triggered build co... [email protected] (JIRA)
- [JIRA] (JENKINS-15214) Triggered build co... [email protected] (JIRA)
- [JIRA] (JENKINS-15214) Triggered build co... [email protected] (JIRA)
- [JIRA] (JENKINS-15214) Triggered build co... [email protected] (JIRA)

Update:
I just found out that the plugin worked only the very first time and only for the first job.
Now Jenkins is ignoring any configuration of the plugin I throw at it for new jobs, while even the first job got problems: it's stucked with the very first value of the tag parameter I configured the first time, and any attempt to change it in subsequent builds is ignored by Jenkins.
T_T
I'm going to delete all the jobs, uninstall the plugin, reinstall / recreate all and letting you know.