• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: pipeline
• Labels:

  • jenkins
  • multi-branch
  • scanmultibranchpipelinenow
• Environment:

  Jenkins 2.401.1
  

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

LD created issue - 2023-07-27 04:37

LD made changes - 2023-07-27 04:38

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?

Mark Waite made changes - 2023-07-27 15:47

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

LD made changes - 2023-07-27 23:48

Resolution	Original: Not A Defect [ 7 ]
Status	Original: Closed [ 6 ]	New: Reopened [ 4 ]

Mark Waite made changes - 2023-07-28 00:06

Status

Original: Reopened [ 4 ]

New: In Progress [ 3 ]

Mark Waite made changes - 2023-07-28 00:06

Status

Original: In Progress [ 3 ]

New: Open [ 1 ]

Mark Waite made changes - 2023-07-28 00:07

Assignee

Original: Denis Saponenko [ vaimr ]

Mark Waite made changes - 2023-07-28 00:08

Component/s		New: pipeline [ 21692 ]
Component/s	Original: pipeline-multibranch-defaults-plugin [ 21926 ]

LD made changes - 2023-07-28 00:41

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]