• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: msbuild-plugin
• Labels:

  • windows
• Environment:

  Win7 in Dutch, Jenkins v2.46, MSBuild Plugin v1.27

[JENKINS-42284] 'chcp' is not recognized as an internal or external command, operable program or batch file.

Roel van Nuland created issue - 2017-02-23 15:00

Roel van Nuland made changes - 2017-02-23 15:00

Description

Original: After upgrading from MSBuild Plugin v1.26 to v1.27, all builds using MSBuild plugin failed with: {code:none}'chcp' is not recognized as an internal or external command, operable program or batch file.{code} This seems to be released with case: JENKINS-24132. As a work-around, i (manually) reverted to MSBuild Plugin v1.26. Running {{chcp}} on the same machine works, running {{chcp}} via the Jenkins script console yields the same error. Running {{chcp.com}} via the Jenkins script console works. Can we please change {{chcp}} to {{chcp.com}}?

New: After upgrading from MSBuild Plugin v1.26 to v1.27, all builds using MSBuild plugin failed with: {code:none}'chcp' is not recognized as an internal or external command, operable program or batch file.{code} This seems to be related to case: JENKINS-24132. As a work-around, i (manually) reverted to MSBuild Plugin v1.26. Running {{chcp}} on the same machine works, running {{chcp}} via the Jenkins script console yields the same error. Running {{chcp.com}} via the Jenkins script console works. Can we please change {{chcp}} to {{chcp.com}}?

Lionel Cabasson made changes - 2017-10-07 16:15

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Kalle Niemitalo made changes - 2021-01-09 15:43

Remote Link

New: This issue links to "[JENKINS-42284] Fix for chcp errors · Pull Request #32 · jenkinsci/msbuild-plugin (Web Link)" [ 26434 ]