Plugin unable to find existing tool path
krishna3008 opened this issue · 1 comments
krishna3008 commented
Jenkins and plugins versions report
Environment
Paste the output here
What Operating System are you using (both controller, and any agents involved in the problem)?
Windows 10 (Latest) (PC | Kubernates)
Ubuntu (Latest) (Kubernates)
Reproduction steps
- https://plugins.jenkins.io/plasticscm-plugin/ outlines the tool configuration has to be set up if not set it will use the existing node configuration.
- But when even I didn't set the configuration also it is trying to install the latest client and getting failed even the latest plastic client is installed in the node
- I tried the
cm version
command by myself it is printing the result but the plugin is still unable to find it. - In nodes the download is getting failed due to the proxy server doesn't allow the installation. so, the pipeline is getting failed due to this.
- The Command I have used is as very old one
scmVars = cm (branch: "${Branch_Name}", changeset: "${Change_set}", cleanup: 'DELETE', repository: "${Repo_Name}", server: "${Plastic_Server}:${Plastic_Port}")
(which should use the existing configuration and system client path) - I am also facing this in the Linux OS too.
Expected Results
C:\h\w>cm version
11.0.16.7303
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] cm
Checking whether tool 'Default' exists in path 'cm'...
$ cm version
11.0.16.7303
Plastic SCM tool is found in system.
Executing cmd /Q script inside container auto of pod test-20-v8zgp-l7vng-0x0fn
Microsoft Windows [Version 10.0.17763.3287]
(c) 2018 Microsoft Corporation. All rights reserved.
Actual Results
C:\h\w>cm version
11.0.16.7303
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] cm
Checking whether tool 'Default' exists in path 'cm'...
$ cm version
Plastic SCM tool not found in system at 'cm': Cannot run program "cm": CreateProcess error=2, The system cannot find the file specified
Unpacking https://www.plasticscm.com/download/clientbundle/latest/client-windows.zip to /h/tools/plasticscm-cli/Default on test-20-v8zgp-l7vng-0x0fn
Executing cmd /Q script inside container auto of pod test-20-v8zgp-l7vng-0x0fn
Microsoft Windows [Version 10.0.17763.3287]
(c) 2018 Microsoft Corporation. All rights reserved.
Anything else?
PLease fix this issue to make the plugin to find the tool.
I am also facing this in the Linux OS too.
mig42 commented
Hi @krishna3008 ,
Thanks for your report. From the output trace you shared, the plugin is unable to find the cm
tool installed in the container.
- How did you install that global
cm
for the machine? What's its current location? - What's the value for the
PATH
environment value in the current session for the running process? Can you share it with us?