Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
Windows server 2012 64 bit, Debian 8
Description
The multibranch project plugin always creates the workspaces to build the branches in "${JENKINS_HOME}/jobs/your-multi-branch-project/branches/${branchNameEncoded}/workspace", however our configuration has the workspaces on a different drive with much more space, so WORKSPACE is not on the same drive as JENKINS_HOME.
This is configured in the global config->Workspace Root Directory (under advanced below Home Directory).
Please use "${Workspace Root Directory}/${branchNameEncoded}/workspace" or something similar instead.
Attachments
Issue Links
- is duplicated by
-
JENKINS-39667 PIpeline job ignores custom workspace location
-
- Resolved
-
- is related to
-
JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named.
-
- Resolved
-
- relates to
-
JENKINS-21942 Unreliable defaulting of Jenkins.workspaceDir
-
- Open
-
- links to
Code changed in jenkins
User: Stephen Connolly
Path:
src/main/java/jenkins/branch/WorkspaceLocatorImpl.java
src/test/java/jenkins/branch/WorkspaceLocatorImplTest.java
http://jenkins-ci.org/commit/branch-api-plugin/16108110bf6e508ccce5bc5102688f35c5bc4287
Log:
Merge pull request #103 from jglick/customMasterDir-
JENKINS-38837JENKINS-38837Handle custom master workspace directoryCompare: https://github.com/jenkinsci/branch-api-plugin/compare/bb1f94f98f51...16108110bf6e