Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-34377

job-restrictions Job Property does not support Pipeline Plugin

      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'

        1. screenshot-1.png
          screenshot-1.png
          5 kB
        2. job-restrictions.hpi
          62 kB
        3. Captura.PNG
          Captura.PNG
          18 kB

          [JENKINS-34377] job-restrictions Job Property does not support Pipeline Plugin

          Daniel Hernandez created issue -
          Daniel Hernandez made changes -
          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:









          Daniel Hernandez made changes -
          Attachment New: Captura.PNG [ 32498 ]
          Daniel Hernandez made changes -
          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'









          Daniel Hernandez made changes -
          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'









          Dominik Ruf made changes -
          Link New: This issue is blocked by JENKINS-36626 [ JENKINS-36626 ]
          Dominik Ruf made changes -
          Link Original: This issue is blocked by JENKINS-36626 [ JENKINS-36626 ]
          Dominik Ruf made changes -
          Link New: This issue is related to JENKINS-36626 [ JENKINS-36626 ]
          Dominik Ruf made changes -
          Component/s New: workflow-plugin [ 18820 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 170479 ] New: JNJira + In-Review [ 183917 ]
          Andrew Bayer made changes -
          Component/s New: pipeline-general [ 21692 ]

            mansoor Mansoor Saqib
            daniel_alejandro_hc Daniel Hernandez
            Votes:
            21 Vote for this issue
            Watchers:
            25 Start watching this issue

              Created:
              Updated: