I am assuming that you are talking about the builds directory under the
jobs/project directory.
This directory is needed by the master so that it can provide the build
history pages and allow access to any archived objects, so this means that
it cannot be located on the slaves as a slave can be offline or removed.
Only the workspaces can be on slaves as Jenkins assumes that these
are disposable and can be relocated to another slave when required.
However you can relocate this build data and artifacts to another location,
that the master can access, this is done via the Manage Jenkins/Configure
System -> Build Record Root Directory item (part of the first advanced
section under Home directory item)
By default this is set to ${ITEM_ROOTDIR}/builds which gives
<jenkins_root>/jobs/<project/job name>/builds
if you want to move this to another location you can set it as
/my_path_to_a_large_network_drive/${ITEM_FULLNAME}/builds
You should use ${ITEM_FULLNAME} in the path as omitting it means that all
builds for every job get put in the same location causing issues elsewhere.
If you are building on master and want the workspace for that in a
different location set the Workspace Root Directory item (This is for the
master only, slaves have their own config)
The job config and next build number both still still stays under the path
<jenkins_root>/jobs/config.xml
hope this helps
Chris,
On Wednesday, 16 May 2012 17:58:25 UTC+1, gerjesjo wrote:
>
> Hello,
>
> We have a jenkins default jobs folder which gets created under master
> home directory which has references of every job logs being built
> within of jenkins. Is there a way to change this to the slaves based
> on each job being tied to so that jobs directory gets created under
> slave folder along with the workspace being set.
>
>
>
