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
IIUC the a master with zero executors will still retrieve the entire repository into the master's workspace directories for each Jenkinsfile it wants to read. I'm seeing this with Jenkins 2.19.4, Branch API Plugin 1.11.1, Git plugin 3.0.1.