Jenkins Plugin: Scanner failed to run properly. Cannot run --http-proxy

L1 Bithead

Jenkins Plugin: Scanner failed to run properly. Cannot run --http-proxy

Given Jenkins running in a container

And Prisma Cloud Jenkins Plugin

And Dashboard View Plugin

And Static Analysis Utilities

And Jenkins Pipeline project

And this Jenkinsfile

And a corporate http(s) proxy

When I choose to Build the project

Then the plugin fails to generate proper shell command

And Jenkins Console reports the following...

Console Output

Started by user tommy hunt
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/prismacloud-pipeline[Pipeline] {[Pipeline] stage[Pipeline] { (Build)[Pipeline] echoDO NOTHING[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Scan)[Pipeline] prismaCloudScanImage[PRISMACLOUD] Scanning images on master
[PRISMACLOUD] Waiting for scanner to complete
[PRISMACLOUD] --http-proxy /var/jenkins_home/workspace/prismacloud-pipeline/twistcli3673897521178042205 images scan nginx:latest --docker-address unix:///var/run/docker.sock --ci --publish --details --address --ci-results-file prisma-cloud-scan-results.json
[prismacloud-pipeline] $ --http-proxy /var/jenkins_home/workspace/prismacloud-pipeline/twistcli3673897521178042205 images scan nginx:latest --docker-address unix:///var/run/docker.sock --ci --publish --details --address --ci-results-file prisma-cloud-scan-results.json
[PRISMACLOUD] Scanner failed to run properly. Cannot run program "--http-proxy" (in directory "/var/jenkins_home/workspace/prismacloud-pipeline"): error=2, No such file or directory[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] prismaCloudPublish[PRISMACLOUD] Publishing analysis results
[PRISMACLOUD] No matching scan result files were found[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: Build failed
Finished: FAILURE


Notice this plugin attempted to execute "--http-proxy" as a shell command.

"--http-proxy" is a global option that should be included with the twistcli shell command.

How can I fix this?

What am I doing wrong?

L0 Member

I am seeing the same issue in almost identical circumstances. Are there any workarounds for this? 


Is it possible to use the twistlock Jenkins plugin with the newer version of the Prisma Cloud Console?



Tags (3)
L2 Linker


Thanks for reaching out. What version of Compute/TL are you running? Have you recently upgraded? For Compute 20.04.x you will require the Jenkins v2 plugin. Additionally, ensure your proxy configuration is set properly, both, in the console and in Jenkins under Manage > Advanced Settings. There are a few things to consider here, but that is a pretty good start.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!