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

durable-task 1.7 breaks workflow bat steps

    XMLWordPrintable

Details

    • 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

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-33456 durable-task 1.8 breaks workflow bat steps

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-27419 dos "exit" command not functioning correctly

          • Major - Major loss of function.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-34150 Pipeline Batch hangs

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-40338 Linux Master and Windows Slave ends up with unusable PATH

          • Major - Major loss of function.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-28718 withTool

          • Major - Major loss of function.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            View 4 older comments
            gordin Christoph Vogtländer added a comment -

            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.

            gordin Christoph Vogtländer added a comment - 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.
            hrmpw Patrick Wolf added a comment -

            Can you reproduce this on the latest version of the durable task plugin?

            hrmpw Patrick Wolf added a comment - Can you reproduce this on the latest version of the durable task plugin?
            jglick Jesse Glick added a comment -

            gordin 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.

            jglick Jesse Glick added a comment - gordin 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.
            jglick Jesse Glick added a comment -

            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.

            jglick Jesse Glick added a comment - 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.
            allenfisher Allen Fisher added a comment -

            I'm having the same issue that gordin 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.

            allenfisher Allen Fisher added a comment - I'm having the same issue that gordin 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.

            People

              jglick Jesse Glick
              gordin Christoph Vogtländer
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: