-
New Feature
-
Resolution: Unresolved
-
Major
-
Jenkins 1.656
job-restrictions-plugin does not support Pipeline Plugin (aka Workflow plugin) and it's behavior is not as expected.
Steps to reproduce it:
Create a job using Pipeline Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin)
Create a slave in your master called for example 'demo-slave'.
In your Groovy script using pipeline do:
node('master') {
}
node('demo-slave') {
}
After in 'demo-slave' configuration, restrict it:
No matter if you start your job with 'daniel_hernandez' user or other user, the job will not get a executor from the demo-slave node getting the message:
Waiting for next available executor on demo-slave
After, You can release it setting the value to 'Take any job'
- is related to
-
JENKINS-36626 Support folder plugin with pipeline
-
- Resolved
-
Hi !, sorry I couldn't replied quick. Regarding this "cancel jobs not meeting this restriction" sounds great, I just wonder oleg_nenashev mansoor why this behavior cant be as default? What would be the reason to hang the process? If the user can't run jobs in that Node and then it hangs , how this job will be released?
I hope to test it again by this weekend.
Thanks !