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

Support of "customWorkspace" is missing for kubernets-plugin

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The functionality to set 'customWorkspace' has been added to agents to bypass problems especially in multibranch projects where branch naming follows 'gitflow' or a simliar approach. There branch-names are e.g. "feature/XY". This leads to default workspace paths aligned with job names and encoded by branch-api plugin to '...feature%2FXY'.

      This workspace paths cause a lot of build tools to fail e.g. maven, ant, ...

      As already stated without this override functionality by 'customWorkspace' this problem is not solvable which means eighter to dont use multibranch in such cases, do not use jenkins fpr such builds or hack the "branch-api" plugin to use a more not conflicting encoding.

      My approach was hacking where i modified url encoding to some non url encoded approach
      e.g. use 'x2F' and not '%2F'

      With support of 'customWorkspace' it will be possible to set such path in pipeline and leave default be default.

        Attachments

          Issue Links

            Activity

            Hide
            bparsapo Bahram Parsapour added a comment -

            Winfried Wasser did you had a chance to test the latest version of the plugin? If so, does it solve your problems described here?

            Show
            bparsapo Bahram Parsapour added a comment - Winfried Wasser did you had a chance to test the latest version of the plugin? If so, does it solve your problems described here?
            Hide
            wwasser Winfried Wasser added a comment -

            seems to work now with a small weak spot:

             It can be either a relative path, in which case the custom workspace will be under the workspace root on the node, or an absolute path.

            The current implementation uses jenkins home as root for relative path and not the configured workspace root.

            Show
            wwasser Winfried Wasser added a comment - seems to work now with a small weak spot:  It can be either a relative path, in which case the custom workspace will be under the workspace root on the node, or an absolute path. The current implementation uses jenkins home as root for relative path and not the configured workspace root.

              People

              • Assignee:
                Unassigned
                Reporter:
                wwasser Winfried Wasser
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: