Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
Description
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.
Attachments
Issue Links
- 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
-
aszostak I get that warning too. The primary reason for the error is the class loader for plugins is only populated with related plugins in which it depends. Since the job-restrictions plugin does not directly depend on pipeline plugins, the class loader for it does not include the workflow set of classes. You're right that you can ignore the error and it will "just work". Can probably be considered a bug. It should probably be using the uber classloader which exists in the plugin manager.