jenkinsci / jenkinsci/workflow-durable-task-step-plugin

[JENKINS-66971] bat command in not executing fromwin 2019 node

Open
#587 1 comment 0 reactions 0 assignees View on GitHub
component:workflow-durable-task-step-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
46
Forks
110
PR merge metrics
No merged PRs in 30d

Description

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 

---
Originally reported by selvatrichy, imported from: bat command in not executing fromwin 2019 node


  • assignee: bluersw
  • status: Open
  • priority: Minor
  • component(s): workflow-durable-task-step-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 2
  • imported: 20251212-090250

Raw content of original issue

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 

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.