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

Scan multibranch pipeline now always runs on built in node

      I am running Jenkins in docker.

      I labled master node (docker) and also set executers to 0.

      Still Scan multibranch pipeline always run on n built in master node and not on build agents (set up using EC2). It appears to ignore any labelling or executers set to 0. 

      All my jobs runs on build agents as they should as built in master node is labled and have 0 executers.

      Is this default behaviour or bug? How can i run scans on build agents?

       

          [JENKINS-71718] Scan multibranch pipeline now always runs on built in node

          Mark Waite added a comment -

          This is the expected behavior. Scans of multibranch Pipelines are performed on the controller (we stopped using the word "master" to describe the controller years ago). When the scan detects a job that needs to be run (or created and run), that run is performed on an agent if the controller has 0 executors.

          Mark Waite added a comment - This is the expected behavior. Scans of multibranch Pipelines are performed on the controller (we stopped using the word "master" to describe the controller years ago). When the scan detects a job that needs to be run (or created and run), that run is performed on an agent if the controller has 0 executors.

          LD added a comment -

          Thanks markewaite for the response.

          Can this be changed by any configuration? I have too many jobs running Scans and that is causing too many scans in waiting queue. If I could use build agents this could be much faster. This does not sound like scalable solution to restrict the running of Scans on controller.

          LD added a comment - Thanks markewaite for the response. Can this be changed by any configuration? I have too many jobs running Scans and that is causing too many scans in waiting queue. If I could use build agents this could be much faster. This does not sound like scalable solution to restrict the running of Scans on controller.

          LD added a comment -

          Hi 

          Reopening. 

          Please confirm if there is any configuration change i can do to change this behaviour or this cannot be changed. 

           

          LD added a comment - Hi  Reopening.  Please confirm if there is any configuration change i can do to change this behaviour or this cannot be changed.   

          Mark Waite added a comment -

          I'm not aware of any way to change it.

          Mark Waite added a comment - I'm not aware of any way to change it.

          LD added a comment -

          Thanks. I will raise a feature request.

          LD added a comment - Thanks. I will raise a feature request.

          LD added a comment -

          I am closing this ticket as I raised an improvement request

          https://issues.jenkins.io/browse/JENKINS-71730

          LD added a comment - I am closing this ticket as I raised an improvement request https://issues.jenkins.io/browse/JENKINS-71730

            Unassigned Unassigned
            ld_singh LD
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: