[JIRA] (JENKINS-53405) Support of "customWorkspace" is missing for kubernets-plugin
Title: Message Title Winfried Wasser commented on JENKINS-53405 Re: Support of "customWorkspace" is missing for kubernets-plugin 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53405) Support of "customWorkspace" is missing for kubernets-plugin
Title: Message Title Winfried Wasser created an issue Jenkins / JENKINS-53405 Support of "customWorkspace" is missing for kubernets-plugin Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2018-09-04 12:45 Labels: git pipeline user-experience Priority: Major Reporter: Winfried Wasser 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.
