-
Bug
-
Resolution: Unresolved
-
Minor
-
None
Recently,
I started to use the Jenkin pipeline and migrating my jobs to pipeline.
It has been noticed that node with 2012 win os is executing (pipeline generated batch command) but not win 2019 node.
Please have a look
(1) Not Jenkins version-specific. Tried with Jenkins 2.289.3 and Jenkins 2.303.2. Issue replicable in both
(2) Node os win 2019 / 64bit os and 64 bit processor
the following code will be executed successfully in win 2012 box but getting skipped in 2019 windows
bat 'C:\\JenKin_Jobs
NetUSeIDrive.bat' ( Have some echo in batch and console in pipeline will not show those echo in 2019 box execution )
We have the workaround to execute as PowerShell but wanted to report the issue
I changed the component from agent-server-parameter-plugin to workflow-durable-task-step-plugin because that is where the bat step is implemented. However, I am not sure this is actually a bug in that plugin.
To find the cause of the problem, please use Process Monitor on the Jenkins agent computer to monitor these events:
The CreateFile events will then show whether cmd.exe tries to open NetUSeIDrive.bat and whether it succeeds. If cmd.exe does not even attempt to open that, you can then look at the other events and perhaps find why.