|
||||||||
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-14197) Plugin is preventi... jswa...@alohaoi.com (JIRA)
- [JIRA] (JENKINS-14197) Plugin is pre... mweb...@java.net (JIRA)
- [JIRA] (JENKINS-14197) Plugin is pre... erwa...@java.net (JIRA)
- [JIRA] (JENKINS-14197) Plugin is pre... af...@java.net (JIRA)
- [JIRA] (JENKINS-14197) Plugin is pre... ohtake_tomoh...@java.net (JIRA)
- [JIRA] (JENKINS-14197) Plugin is pre... deepak.ar...@ch1group.com (JIRA)
- [JIRA] (JENKINS-14197) Plugin is pre... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14197) Plugin is pre... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14197) Plugin is pre... ohtake_tomoh...@java.net (JIRA)
I had another problem with 2.6 which I think is part of this problem:
I noticed that we had a number of jobs waiting for executors, but the master and all slaves were idle. Restarting the master did not help. I seem to recall that the affected jobs previously had “restrict where this project can run” set, but now it’s unset. I had to downgrade Promoted-Builds to v2.5, and then reenter the “restrict where this project can run” value in the job config.