[JIRA] [workflow-plugin] (JENKINS-34032) Pipeline plugin workflow step allocates workspace in jenkins root
Title: Message Title Jesse Glick resolved as Not A Defect Jenkins / JENKINS-34032 Pipeline plugin workflow step allocates workspace in jenkins root Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34032) Pipeline plugin workflow step allocates workspace in jenkins root
Title: Message Title Axel von Engel commented on JENKINS-34032 Re: Pipeline plugin workflow step allocates workspace in jenkins root Oops, seems I misinterpreted the documentation as "relative to the workspace root". Anyway, thanks for the suggestion to use a relative path Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34032) Pipeline plugin workflow step allocates workspace in jenkins root
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-34032
Pipeline plugin workflow step allocates workspace in jenkins root
According to the documentation given in Snippet Generator:
The path may be relative to the slave root, or absolute.
Now perhaps it would be more intuitive to use Jenkins.getRawWorkspaceDir() or Slave.getWorkspaceRoot() as the base directory if an absolute path is not used. Not sure that such a change would be compatible, though.
Anyway better would perhaps be to write
ws("${pwd()}/../${env.BRANCH_NAME.replace('/', '-')}") {…}
which will always allocate a workspace which is a sibling of the current one.
Change By:
Jesse Glick
Issue Type:
Bug Improvement
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-34032) Pipeline plugin workflow step allocates workspace in jenkins root
Title: Message Title
Axel von Engel created an issue
Jenkins / JENKINS-34032
Pipeline plugin workflow step allocates workspace in jenkins root
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Apr/05 3:05 PM
Environment:
Jenkins 1.642 & Pipeline 1.14
Priority:
Minor
Reporter:
Axel von Engel
I recently had to allocate a specific workspace due to some tool not being able to cope with url-encoded paths (generated by the multibranch pipeline).
My workaround was to add a workspace step:
ws(env.BRANCH_NAME.replaceAll('/','-')
This resulted in the workspace being /opt/jenkins/feature-new-hot-stuff. My expectation was /opt/jenkins/workspace/feature-new-hot-stuff, though.
Easy workaround: use
ws("workspace/${env.BRANCH_NAME.replaceAll('/', '-')}")
