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

Give the ability to choose how the multibranch subprojects will be named.

      The %2F encoding of / breaks many software (msbuild for example) and can't be changed.
      Being able to provide a rule to build the subproject names from the branch name instead of just encoding things would permit to give the user the power to work around their problems with this kind of software.

      This would be an advanced option in which one can write something like a sed regex.

          [JENKINS-34564] Give the ability to choose how the multibranch subprojects will be named.

          Kevin Grandemange created issue -
          Kevin Grandemange made changes -
          Description Original: The %2F encoding of / breaks many software (msbuild for example) and can't be changed.
          Being able to provide a rule to build the subproject names from the branch name instead of just encoding things would permit to give the user the power to workaround their problems with this kind of software.

          This would an advanced option in which one can write something like a sed regex.
          New: The %2F encoding of / breaks many software (msbuild for example) and can't be changed.
          Being able to provide a rule to build the subproject names from the branch name instead of just encoding things would permit to give the user the power to work around their problems with this kind of software.

          This would be an advanced option in which one can write something like a sed regex.
          heinzepreller made changes -
          Link New: This issue is duplicated by JENKINS-34595 [ JENKINS-34595 ]

          Michael Neale added a comment - - edited

          This also breaks tools like "npm run" as well (even on filesystems where it is ok).

          "%" is not recommended as a path name on any platform, even if it is tolerated in some cases.
          I think the %2F causes more problems that people realise, so picking something else would make more sense vs making it an "advanced" option.

          Michael Neale added a comment - - edited This also breaks tools like "npm run" as well (even on filesystems where it is ok). "%" is not recommended as a path name on any platform, even if it is tolerated in some cases. I think the %2F causes more problems that people realise, so picking something else would make more sense vs making it an "advanced" option.

          Jesse Glick added a comment -

          Not easily changed. There is a bidirectional mapping between branch name and job name which must be recoverable. Also existing branch projects must be preserved, and these are already using URL encoding. So I do not plan to change the job names.

          The workspace name is another matter. Possibly Jenkins core could just use a different algorithm for Jenkins/Slave.getWorkspaceFor which uses blander characters.

          Jesse Glick added a comment - Not easily changed. There is a bidirectional mapping between branch name and job name which must be recoverable. Also existing branch projects must be preserved, and these are already using URL encoding. So I do not plan to change the job names. The workspace name is another matter. Possibly Jenkins core could just use a different algorithm for Jenkins/Slave.getWorkspaceFor which uses blander characters.

          Jesse Glick added a comment -

          Not a blocker since you can trivially customize the workspace you use from within Jenkinsfile itself, using the ws step.

          Jesse Glick added a comment - Not a blocker since you can trivially customize the workspace you use from within Jenkinsfile itself, using the ws step.
          Jesse Glick made changes -
          Priority Original: Blocker [ 1 ] New: Major [ 3 ]
          Jesse Glick made changes -
          Link New: This issue duplicates JENKINS-30744 [ JENKINS-30744 ]
          Jesse Glick made changes -
          Labels New: multibranch

          Michael Neale added a comment -

          yes I think the only real problem is % in the path.

          This is the best I can find (it isn't much) for what to not use in a path:

          https://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words

          I would class this as an "ongoing irritation" to keep an eye on.

          Michael Neale added a comment - yes I think the only real problem is % in the path. This is the best I can find (it isn't much) for what to not use in a path: https://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words I would class this as an "ongoing irritation" to keep an eye on.

            jglick Jesse Glick
            rkutic Kevin Grandemange
            Votes:
            59 Vote for this issue
            Watchers:
            84 Start watching this issue

              Created:
              Updated:
              Resolved: