-
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
-
[JENKINS-34377] job-restrictions Job Property does not support Pipeline Plugin
Description | Original: job-restrictions-plugin does not support Pipeline Plugin (aka Workflow plugin) and it's behavior is not as expected. |
New:
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: |
Attachment | New: Captura.PNG [ 32498 ] |
Description |
Original:
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: |
New:
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: !Captura.PNG|thumbnail! No matter if start your job with 'daniel_hernandez' user or other user, the job will not get a executor from the demo-slave node gettint the message: *Waiting for next available executor on demo-slave* *After*, You can release it setting the value to 'Take any job' |
Description |
Original:
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: !Captura.PNG|thumbnail! No matter if start your job with 'daniel_hernandez' user or other user, the job will not get a executor from the demo-slave node gettint the message: *Waiting for next available executor on demo-slave* *After*, You can release it setting the value to 'Take any job' |
New:
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: !Captura.PNG|thumbnail! 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' |
Link |
New:
This issue is blocked by |
Link |
Original:
This issue is blocked by |
Link |
New:
This issue is related to |
Component/s | New: workflow-plugin [ 18820 ] |
Workflow | Original: JNJira [ 170479 ] | New: JNJira + In-Review [ 183917 ] |
Component/s | New: pipeline-general [ 21692 ] |