Status: Resolved (View Workflow)
When using job restrictions plugin, I want to be able to restrict slaves to only run jobs that are in a certain folder. This should be an easy change.
Joakim Ahle made changes -
|Field||Original Value||New Value|
|Description||When using job restrictions plugin, I want to be able to restrict slaves to only run jobs that are in a certain folder. This should be an easy change.|
|Assignee||Joakim Ahle [ joakim_ahle ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
R. Tyler Croy made changes -
|Workflow||JNJira [ 156379 ]||JNJira + In-Review [ 195394 ]|
Torsten Tuchscheerer made changes -
[ I tested the plugin and for me it looks like that the pattern for a folder is not compared correctly?! May be I'm wrong and I use the settings not in the way I should. Unfortunately I did not found an example which covers my needs.
What I did is the following:
I have a Linux slave connected via SSH. In the node configuration I enabled the plugin and selected _Regular expression (Job Name)_. In the _expression_ field I added _*Linux/**_ - this is a folder where all projects are created which should run on the Linux slave. Additionally I added a value for _Labels_ which is identically with the FQDN of the slave.
In a project which is a child of the the _*Linux*_ folder I added the value of the slave FQDN in the field _Restrict where this project.._.
When I start a job now manually it does not start - it's waiting for the next available executor.
Could you give me a hint what's wrong with my setup? The same behavior for a Windows slave.
* Jenkins 2.32.3
* Project base matrix authorization 1.4
* Plugin version 0.6 (also 0.5 was tested) ]