|
|
_0.png) |
|
|
|
|
Issue Type:
|
Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
promoted-builds |
|
Created:
|
24/Jun/12 12:48 AM
|
|
Description:
|
With Promoted-Builds v2.6 installed, it is no longer possible to set the "Restrict where this project can be run". Any value in the field is not committed when the job is saved.
NOTE: Downgrading Promoted-Builds to v2.5 resolved the problem.
|
|
Environment:
|
Windows 2008, Jenkins 2.471, Promoted-Builds 2.6
|
|
Project:
|
Jenkins
|
|
Labels:
|
jenkins
promoted-builds
plugin
slave
|
|
Priority:
|
Blocker
|
|
Reporter:
|
Jason Swager
|
|
|
|
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
|
|
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.