-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.401.1
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
LD
created issue -
LD
made changes -
| Description |
Original:
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). Is this default behaviour or bug? How can i run scans on build agents? |
New:
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? |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
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.
LD
made changes -
| Resolution | Original: Not A Defect [ 7 ] | |
| Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
| Status | Original: Reopened [ 4 ] | New: In Progress [ 3 ] |
| Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
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.