[JENKINS-25783] very long build directory paths are created by Matrix project, and difficult directcory names #593

Activity

1. jenkins-infra-bot commented on Nov 25, 2014

   

   jenkins-infra-bot

   on Nov 25, 2014

   Author

   More actions

   danielbeck:

   • Comment link
   • Original comment link (no redirect)
   • Raw content of original comment:

     (note to self: read first, then comment  )
     

   (note to self: read first, then comment )
2. jenkins-infra-bot commented on Feb 28, 2015

   

   jenkins-infra-bot

   on Feb 28, 2015

   Author

   More actions

   spikerjenk2:

   • Comment link
   • Original comment link (no redirect)
   • Raw content of original comment:

     Label expression axis can also create bad paths.  If I have "label1&&label2" expression, the path then include /job/label1&&label2/...
     
     This makes for some nasty workarounds in shell scripts.
     

   Label expression axis can also create bad paths. If I have "label1&&label2" expression, the path then include /job/label1&&label2/...

   This makes for some nasty workarounds in shell scripts.
3. jenkins-infra-bot commented on Feb 28, 2015

   

   jenkins-infra-bot

   on Feb 28, 2015

   Author

   More actions

   danielbeck:

   • Comment link
   • Original comment link (no redirect)
   • Raw content of original comment:

     spikerjenk2: Wouldn't it suffice to just consistently double-quote references to the folder? What specifically breaks?
     

   spikerjenk2: Wouldn't it suffice to just consistently double-quote references to the folder? What specifically breaks?
4. jenkins-infra-bot commented on Feb 28, 2015

   

   jenkins-infra-bot

   on Feb 28, 2015

   Author

   More actions

   bachp:

   • Comment link
   • Original comment link (no redirect)
   • Raw content of original comment:

     You are right if the path was quoted correctly everywhere there would be no issue. However if you build a whole linux distribution with hundreds of third party packages it is very likely that some components get it wrong. To fix this is a huge effort and not possible to fix in the short term.
     So I also would appreciate an option that would allow to get more "standard" paths.
     

   You are right if the path was quoted correctly everywhere there would be no issue. However if you build a whole linux distribution with hundreds of third party packages it is very likely that some components get it wrong. To fix this is a huge effort and not possible to fix in the short term.
   So I also would appreciate an option that would allow to get more "standard" paths.
5. jenkins-infra-bot commented on Feb 28, 2015

   

   jenkins-infra-bot

   on Feb 28, 2015

   Author

   More actions

   spikerjenk2:

   • Comment link
   • Original comment link (no redirect)
   • Raw content of original comment:

     @Daniel @Pascal
     
     The worst offender is python virtualenv.  Wrapper scripts insert the shebang of the interpreter, which is in the workspace.  So "myProg.py" would have
     
     
     #!/path/to/my/job/label1&&label2/venv/bin/python
     ...
     
     
     I unfortunately have to wrap everything in a shell script to re-write the shebang.
     I'd also like to add (most) linux kernels limit the shebang line to 127 characters, which is easily outdone with big matrix jobs.
     

   @​Daniel @​Pascal

   The worst offender is python virtualenv. Wrapper scripts insert the shebang of the interpreter, which is in the workspace. So "myProg.py" would have

   #!/path/to/my/job/label1&&label2/venv/bin/python
   ...
   

   I unfortunately have to wrap everything in a shell script to re-write the shebang.

   I'd also like to add (most) linux kernels limit the shebang line to 127 characters, which is easily outdone with big matrix jobs.
6. jenkins-infra-bot commented on Feb 28, 2015

   

   jenkins-infra-bot

   on Feb 28, 2015

   Author

   More actions

   danielbeck:

   • Comment link
   • Original comment link (no redirect)
   • Raw content of original comment:

     FWIW there's a global (Jenkins-wide) option to use short sub-workspace paths for matrix projects: hudson.matrix.MatrixConfiguration.useShortWorkspaceName
     
     More information on:
     https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties
     

   FWIW there's a global (Jenkins-wide) option to use short sub-workspace paths for matrix projects: hudson.matrix.MatrixConfiguration.useShortWorkspaceName

   More information on:
   https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties
7. jenkins-infra-bot commented on Mar 7, 2015

   

   jenkins-infra-bot

   on Mar 7, 2015

   Author

   More actions

   ringerc:

   • Comment link
   • Original comment link (no redirect)
   • Raw content of original comment:

     Daniel, very useful hint. Thankyou. The applicability of that property sure isn't limited to Cygwin.
     
     Some Windows kernels have bugs relating to deep paths (well short of the official path limit). I've had to abbreviate all my labels to get things to work, and even then it's troublesome.
     
     On *nix, label expressions containing shell metacharacters are "fun". Yes, everything should be carefully quoted. It's a pain when you're working with things like third party shell script snippets in configure scripts though.
     
     Some form of mapping would be very helpful. Or at least exposing this as an advanced matrix build option instead of a system property.
     

   Daniel, very useful hint. Thankyou. The applicability of that property sure isn't limited to Cygwin.

   Some Windows kernels have bugs relating to deep paths (well short of the official path limit). I've had to abbreviate all my labels to get things to work, and even then it's troublesome.

   On *nix, label expressions containing shell metacharacters are "fun". Yes, everything should be carefully quoted. It's a pain when you're working with things like third party shell script snippets in configure scripts though.

   Some form of mapping would be very helpful. Or at least exposing this as an advanced matrix build option instead of a system property.
8. jenkins-infra-bot commented on Jun 9, 2017

   

   jenkins-infra-bot

   on Jun 9, 2017

   Author

   More actions

   jglick:

   • Comment link
   • Original comment link (no redirect)
   • Raw content of original comment:

     Better solved more generically, as in JENKINS-30148.
     

   Better solved more generically, as in JENKINS-30148.
9. jenkins-infra-bot

   closed this as completedon Jun 9, 2017
10. jenkins-infra-bot commented on Dec 6, 2025

    

    jenkins-infra-bot

    on Dec 6, 2025

    Author

    More actions

    [Original relates_to from Jira: JENKINS-30148]
11. jenkins-infra-bot

    added

    enhancement

    imported-jira-issue

    component:matrix-project-plugin

    resolution:duplicate

    priority:minor

    on Dec 6, 2025