If a job is defined in a folder and tied to a slave or label then it does not show up in the “Projects tied to” report for either /computer/* or /label/*. A job with the same configuration in the root folder does show up in these reports.
The reason is that Label.getTiedJobs calls Jenkins.getItems() which will ignore the contents of folders; should be using getAllItems(AbstractProject.class).
(This call is potentially slow so not a great idea to call synchronously from a Jelly view; better to use ProgressiveRendering. Not as big of an issue as e.g. /asynchPeople for which builds, not just projects, are loaded.)
- is related to
-
JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs
-
- Resolved
-
[JENKINS-15666] Label.getTiedJobs ignores non-top-level jobs
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 146422 ] | New: JNJira + In-Review [ 191928 ] |