-
Bug
-
Resolution: Duplicate
-
Critical
After upgrading to 1.642 - this setting appears to be missing, and jobs are now trying to run anywhere they feel like, which clearly isn't going to work.
The 'assignedNode' element is still present in the configs, but the configuration element is not displayed when editing the job, and doesn't appear to be used at all.
Trying to downgrade to 1.640 (previous release I was running) to confirm that it comes back.
- duplicates
-
-
- Closed
-
[JENKINS-32098] "Restrict where build can run" missing after 1.642 update
Also, would be interesting if you could try 1.641. It only contains the security fixes over 1.640, so should be safe enough.
I don't really see anything in the 1.641-to-1.642 changes that could explain this behavior.
Anything interesting in jenkins.log or /log/all? https://wiki.jenkins-ci.org/display/JENKINS/Logging
Not sure what you mean by "have slaves configured"? There are a dozen or so slaves with labels - and everything looked normal, except when bringing up the edit job screen on 1.642 the option to restrict simply wasn't displayed.
I'll see if I can try 1.641 - I didn't upgrade to it since it didn't resolve the backtrace issue I was seeing. (Other resolved bug.)
1.641 - field is still present in the edit job screen.
going to check 1.642 again just to be certain.
Output of the following in the script console would be interesting:
println Jenkins.instance.labels.size()
println Jenkins.instance.clouds.size()
println Jenkins.getItemByFullName("NameOfYourProject").assignedLabel
println Jenkins.instance.selfLabel
wtf. just replaced war again to take to 1.642 and the option is there. something else was clearly causing this then.
Very confused now.
Confirmed that 1.640 option comes back.