If the job name has spaces in it, then it appears that the generated files for the bat step in the workflow plugin do not correctly escape the file paths and as a result the build ends up hanging. I chased around the code some, and it appears that this is coming from WindowsBatchScript in the durable task plugin. Also, when the build does hang, it does not seem to be possible to terminate it, I ended up having to delete the job folder manually while Jenkins was not running in order to get rid of the active build.

      The workaround is to not have spaces in your job names, but our current naming patterns tend to have spaces and since everything else appears to handle them correctly, it seems like this plugin should as well.

          [JENKINS-27014] Job name with spaces breaks workflow bat step

          Andy Neebel created issue -
          Jesse Glick made changes -
          Link New: This issue duplicates JENKINS-25678 [ JENKINS-25678 ]
          Jesse Glick made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 161205 ] New: JNJira + In-Review [ 196682 ]
          Andrew Bayer made changes -
          Labels Original: windows workflow New: pipeline windows workflow
          Andrew Bayer made changes -
          Labels Original: pipeline windows workflow New: pipeline windows

            jglick Jesse Glick
            andne Andy Neebel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: