-
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
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-