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.
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.
Thanks. Blocker for me too. I noticed the same problem and rollback to promoted build v2.5 solved the problem. (good workaround)
In addition, creating new jobs from another job resets the "restrict where this project can be run" to some other value. It's always the same label for me.
Ran into the same issue. Thanks for the workaround!
Code changed in jenkins
User: OHTAKE Tomohiro
[FIXED JENKINS-14197] Fix preventing setting "Restrict where this project can be run"
Thx very much, this is really a terrible bug... hope this bug can be fixed asap...
I see it's fixed in the source, but when can we expect to pull down the update? This should be a high priority update given the impact on other build aspects.
Promoted Builds 2.6.1 has been released.
It will be available in several hours.
Sorry for inconvenience.