![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
mdonohue
|
|
Attachments:
|
config.xml |
|
Components:
|
join |
|
Created:
|
06/Feb/13 4:07 PM
|
|
Description:
|
Our buildmeister updated all of our plugins to the latest versions (I can create a list if necessary) and the join trigger no longer reliably executes the end jobs. There are no error messages that we can see in any logs, the end job just does not run. I have attached the configuration of one of the top level job. Please let me know what other data I can supply. This has become a critical issue for us here. There were no intentional changes to configuration files associated with the upgrade of plugins, but there were two steps that jenkins forced us to do. 1) Clean up obsolete configuration 2) re-keying of something. (buildmeister did the upgrades, not me)
We ran several instances of builds before doing the re-keying and the cleanup and the problem existed then as well.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Christopher Knowlton
|
|
|
|
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.
