Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Not A Defect
-
Component/s: pipeline
-
Labels:
-
Environment:Jenkins 2.76, latest plugins for 28.08.2017, Linux, latest Oracle Java 8
-
Similar Issues:
Description
I've just noticed that Multibranch Pipelines are eating the first character of the folder names created inside JENKINS_HOME/worspace. In the following folders, ipeline should be pipeline.
drwxr-xr-x 15 jenkins jenkins 4096 Aug 25 12:08 ipeline_improvements_CDP-43-PCRTH2VH45FBCKQZUA5U7S5WLPQCISSIQVSEXHY7YYUZYNYOLZWQ
{{ drwxr-xr-x 14 jenkins jenkins 4096 Aug 22 18:05 ipeline_improvements_CDP-43-PCRTH2VH45FBCKQZUA5U7S5WLPQCISSIQVSEXHY7YYUZYNYOLZWQ@script}}
{{ drwxr-xr-x 2 jenkins jenkins 4096 Aug 25 11:59 ipeline_improvements_CDP-43-PCRTH2VH45FBCKQZUA5U7S5WLPQCISSIQVSEXHY7YYUZYNYOLZWQ@script@tmp}}
{{ drwxr-xr-x 2 jenkins jenkins 4096 Aug 25 11:59 ipeline_improvements_CDP-43-PCRTH2VH45FBCKQZUA5U7S5WLPQCISSIQVSEXHY7YYUZYNYOLZWQ@tmp}}
Attachments
Activity
The problem with this approach is that the folder can end up starting with a '-' or some other special char. When you pass a foldername as parameter the shell command will actually think the directoryname is another parameter and crash.
My build just crashed due to:
dpkg-source --before-build -Foldername
Hermann Schweizer
added a comment - The problem with this approach is that the folder can end up starting with a '-' or some other special char. When you pass a foldername as parameter the shell command will actually think the directoryname is another parameter and crash.
My build just crashed due to:
dpkg-source --before-build -Foldername 
This is actually deliberate - there's logic for determining and guaranteeing uniqueness of Pipeline workspaces based on the job name that can in some scenarios result in the "head" of the job name being chomped.