Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42284

'chcp' is not recognized as an internal or external command, operable program or batch file.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: msbuild-plugin
    • Labels:
    • Environment:
      Win7 in Dutch, Jenkins v2.46, MSBuild Plugin v1.27
    • Similar Issues:

      Description

      After upgrading from MSBuild Plugin v1.26 to v1.27, all builds using MSBuild plugin failed with:

      'chcp' is not recognized as an internal or external command, operable program or batch file.

      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?

        Attachments

          Activity

          kompjoefriek Roel van Nuland created issue -
          kompjoefriek Roel van Nuland made changes -
          Field Original Value New Value
          Description 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}}?
          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}}?
          marshall777 Lionel Cabasson made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              marshall777 Lionel Cabasson
              Reporter:
              kompjoefriek Roel van Nuland
            • Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: