Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Blocker
-
Resolution: Unresolved
-
Component/s: durable-task-plugin
-
Labels:
-
Environment:Jenkins 1.625.2 and 1.625.3
durable-taks 1.7
workflow plug ins 1.11
-
Similar Issues:
-
Sprint:Pipeline - April 2018
Description
After updating durable-task from 1.6 to 1.7 workflow builds fail to execute bat steps:
[Workflow] bat
[workspace] Running batch script
'cmd' is not recognized as an internal or external command,
operable program or batch file.
After switching back to durable-task version 1.6 everything is working again as expected
Attachments
Issue Links
- is blocking
-
-
- Resolved
-
-
-
- Resolved
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
JENKINS-28718 withTool
-
- Open
-
Activity
Can you reproduce this on the latest version of the durable task plugin?
Christoph Vogtländer Are you using the EnvInject plugin? If so, disable it. At any rate, if there are steps to reproduce from scratch please let us know.
One user reported similar symptoms which seem to have been caused by writing
env.PATH = "${tool 'Maven 3'}/bin:${env.PATH}"
rather than
env.Path = "${tool 'Maven 3'}\\bin;${env.Path}"
(The bad path separator : is the problem; the rest is stylistic.)
An implementation of JENKINS-28718 would offer a cross-platform version of this idiom not susceptible to that mistake.
At any rate, WindowsBatchScript could detect a node whose current %Path% lacks C:\Windows\System32 or generally does not seem to have an entry for cmd.exe, and report this misconfiguration more clearly.
I'm having the same issue that Christoph Vogtländer is having, and the workaround he suggests works for now. This is a very vanilla installation with a fresh Windows 2012 machine. Something is very strange, I am running a powershell script and I had to pass the full path to powershell.exe in order to get Jenkins to find it. The system PATH has PowerShell in it so I'm not sure why that doesn't work either.
Allen Fisher
added a comment - I'm having the same issue that Christoph Vogtländer is having, and the workaround he suggests works for now. This is a very vanilla installation with a fresh Windows 2012 machine. Something is very strange, I am running a powershell script and I had to pass the full path to powershell.exe in order to get Jenkins to find it. The system PATH has PowerShell in it so I'm not sure why that doesn't work either.
In the global Jenkins settings I have set "Prepare jobs environment" -> "Unset System Environment Variables" and I can confirm that this is causing the issue on my master node (why slave nodes are not affected remains unclear to me, the nodes have not specific setting regarding to environment variables).
IMHO bat-steps should still work even if the "Unset System Environment Variables" option is set.