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

job-restrictions Job Property does not support Pipeline Plugin

    XMLWordPrintable

Details

    Description

      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'

      Attachments

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

        Issue Links

          Activity

            daniel_alejandro_hc Daniel Hernandez created issue -
            daniel_alejandro_hc Daniel Hernandez made changes -
            Field Original Value New Value
            Description job-restrictions-plugin does not support Pipeline Plugin (aka Workflow plugin) and it's behavior is not as expected. 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_alejandro_hc Daniel Hernandez made changes -
            Attachment Captura.PNG [ 32498 ]
            daniel_alejandro_hc Daniel Hernandez made changes -
            Description 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:









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









            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'









            domruf Dominik Ruf made changes -
            Link This issue is blocked by JENKINS-36626 [ JENKINS-36626 ]
            domruf Dominik Ruf made changes -
            Link This issue is blocked by JENKINS-36626 [ JENKINS-36626 ]
            domruf Dominik Ruf made changes -
            Link This issue is related to JENKINS-36626 [ JENKINS-36626 ]
            domruf Dominik Ruf made changes -
            Component/s workflow-plugin [ 18820 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 170479 ] JNJira + In-Review [ 183917 ]
            abayer Andrew Bayer made changes -
            Component/s pipeline-general [ 21692 ]
            abayer Andrew Bayer made changes -
            Component/s workflow-plugin [ 18820 ]
            jglick Jesse Glick made changes -
            Component/s pipeline [ 21692 ]
            jglick Jesse Glick made changes -
            Labels pipeline
            oleg_nenashev Oleg Nenashev made changes -
            Summary job-restrictions does not support Pipeline Plugin job-restrictions Job Property does not support Pipeline Plugin
            mansoor Mansoor Saqib made changes -
            Attachment job-restrictions.hpi [ 40128 ]
            danielahcardona Daniel Alejandro Hernández made changes -
            Attachment screenshot-1.png [ 40157 ]
            mansoor Mansoor Saqib made changes -
            Attachment job-restrictions.hpi [ 40128 ]
            mansoor Mansoor Saqib made changes -
            Attachment job-restrictions.hpi [ 40172 ]
            mansoor Mansoor Saqib made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            mansoor Mansoor Saqib made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ] Mansoor Saqib [ mansoor ]

            People

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

              Dates

                Created:
                Updated: