-
Bug
-
Resolution: Unresolved
-
Minor
Trying the job-restrictions-plugin with Workflow jobs - I added a restriction to master that only jobs matching a regex could run on there. At first glance, that looked perfect - a Workflow job that didn't match that regex stayed in queue while another Workflow job that did match ran fine.
But then I realized that the non-matching job was still sitting in queue, even after another executor not on the master was available. The job is just stuck - it's not even getting to the node { }, etc. If it can't run on master (when master has executors), it just flops around. Ow.
- is related to
-
JENKINS-38644 Add the class-name-based job restriction
-
- Resolved
-
-
JENKINS-36626 Support folder plugin with pipeline
-
- Resolved
-
-
JENKINS-51359 Unclear documentation class restriction validation claims classes that exist are not found
-
- Resolved
-
- relates to
-
JENKINS-46652 Authorize Project blocks Pipeline Jobs when Computer/Build for master is lacking
-
- Resolved
-
[JENKINS-31866] Attempts to restrict Pipeline jobs from running on master result in job hanging
Link | New: This issue is related to INFRA-504 [ INFRA-504 ] |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Workflow | Original: JNJira [ 167332 ] | New: JNJira + In-Review [ 182686 ] |
Link |
New:
This issue is related to |
Summary | Original: Attempts to restrict Workflow jobs from running on master result in job hanging | New: Attempts to restrict Pipeline jobs from running on master result in job hanging |
Link |
New:
This issue is related to |
Link |
New:
This issue relates to |
Attachment | New: JenkinsScreenshot.png [ 43259 ] |
Link |
New:
This issue is related to |
Labels | New: pipeline-compatibility |