-
Bug
-
Resolution: Fixed
-
Major
-
Windows 8.1
Jenkins 1.643
Workflow Plugin 1.12
As first reported in JENKINS-30744 windows 'bat' workflow task hangs on the encoding of git branch names when these branches contain special characters (tested with gitflow naming convention that has '/' in the branch name).
The encoded path seems to create problems on windows when using 'bat'.
Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like <workspace_path>/feature%2Fmyfeature@script and <workspace_path>/feature%2Fmyfeature.
When I apply the following workflow in a multibranch job in a root file 'Jenkinsfile', Jenkins hangs forever on the bat command
node {
stage 'Checkout'
checkout scm
stage 'Build'
bat "echo 'test'"
}
When I add this same script on the 'master' branch everything is fine.
- is related to
-
-
- Closed
-
- links to
[JENKINS-32701] Slashes in branch names cause 'bat' workflow task to hang
Jan Arend Jansen
created issue -
Jan Arend Jansen
made changes -
| Link |
New:
This issue is related to |
Jan Arend Jansen
made changes -
| Description |
Original:
As first reported in The encoded path seems to create problems on windows when using 'bat'. Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like <workspace_path>/feature%2Fmyfeature@script and <workspace_path>/feature%2Fmyfeature. When I apply the following workflow in a multibranch job in a root file 'Jenkinsfile', Jenkins hangs forever on the bat command node { stage 'Checkout' checkout scm stage 'Build' bat "echo 'test'" } When I add this same script on the 'master' branch everything is fine. |
New:
As first reported in The encoded path seems to create problems on windows when using 'bat'. Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like <workspace_path>/feature%2Fmyfeature@script and <workspace_path>/feature%2Fmyfeature. When I apply the following workflow in a multibranch job in a root file 'Jenkinsfile', Jenkins hangs forever on the bat command {code} node { stage 'Checkout' checkout scm stage 'Build' bat "echo 'test'" } {code| When I add this same script on the 'master' branch everything is fine. |
Jan Arend Jansen
made changes -
| Description |
Original:
As first reported in The encoded path seems to create problems on windows when using 'bat'. Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like <workspace_path>/feature%2Fmyfeature@script and <workspace_path>/feature%2Fmyfeature. When I apply the following workflow in a multibranch job in a root file 'Jenkinsfile', Jenkins hangs forever on the bat command {code} node { stage 'Checkout' checkout scm stage 'Build' bat "echo 'test'" } {code| When I add this same script on the 'master' branch everything is fine. |
New:
As first reported in The encoded path seems to create problems on windows when using 'bat'. Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like <workspace_path>/feature%2Fmyfeature@script and <workspace_path>/feature%2Fmyfeature. When I apply the following workflow in a multibranch job in a root file 'Jenkinsfile', Jenkins hangs forever on the bat command {code} node { stage 'Checkout' checkout scm stage 'Build' bat "echo 'test'" } {code} When I add this same script on the 'master' branch everything is fine. |
Would that have a negative effect on anything?
Yes, at least potentially.
| Labels | Original: workflow | New: multibranch workflow |
| Remote Link | New: This issue links to "PR 16 (Web Link)" [ 14112 ] |
| Assignee | Original: Jesse Glick [ jglick ] | New: Arthur Schreiber [ arthurschreiber ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Here's a thought I have - why not undo the encoding when creating the workspace path and let have a few more levels of directories? Would that have a negative effect on anything?
Also, this appears to duplicate
JENKINS-30744