-
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
-
JENKINS-32112 NullPointerExceptions about templates in various places
-
- Closed
-
[JENKINS-32098] "Restrict where build can run" missing after 1.642 update
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Cannot Reproduce [ 5 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
Component/s | New: vsphere-cloud-plugin [ 16104 ] | |
Component/s | Original: core [ 15593 ] |
Resolution | Original: Cannot Reproduce [ 5 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 167581 ] | New: JNJira + In-Review [ 198236 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |