-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major
-
Component/s: stackrox-container-image-scanner-plugin
-
None
A problem with jobs running on a controller even when the pipeline mentions a specific agent name
Here is my Pipeline.
// code placeholder pipeline { Â Â agent {label 'my-slave'}Â Â stages { Â Â Â Â stage('Test') { Â Â Â Â Â Â steps { Â Â Â Â Â Â Â Â stackrox ( Â Â Â Â Â Â Â Â Â Â apiToken: 'xxxxx', Â Â Â Â Â Â Â Â Â Â caCertPEM: """-----BEGIN CERTIFICATE----- MIIxxxxxxx -----END CERTIFICATE-----""", Â Â Â Â Â Â Â Â Â Â enableTLSVerification: false, Â Â Â Â Â Â Â Â Â Â failOnCriticalPluginError: true, Â Â Â Â Â Â Â Â Â Â failOnPolicyEvalFailure: true, Â Â Â Â Â Â Â Â Â Â portalAddress: 'https://mystackrox:443', Â Â Â Â Â Â Â Â Â Â imageNames: "nginx:latest" Â Â Â Â Â Â Â Â ) Â Â Â Â Â Â } Â Â Â Â } Â Â } }
Â
The pipeline was supposed to run on "my-agent" since we wanted to have restricted access to our stackrox only from the agent, but it's running on Controller/Master even though we've explicitly mentioned agent.
