On Thu, Sep 6, 2012 at 8:50 AM, Jerome Lacoste <[email protected]> wrote:
> I am trying to centralize on my master the list of files required for my
> various slaves.
>
[...]
> Possible "simple" implementations:
> * a directory on the slave that automatically gets synced with the master on
> a particular location e.g. JENKINS_HOME/slaveContent/$slaveName/
> * a file upload mechanism from Jenkin's web GUI ? (where I could upload
> files into userContent - or a perSlave directory)
We just use a common nfs/samba read-only file share for the tools and
common libraries needed on the slaves. It's not particularly secure
against reading (just IP based restrictions), but files can only be
changed on the master which happens to be the host. If network speed
is an issue for runtime access, you could rsync copies locally in a
job that could be scheduled or manual. For our own library
components, we use svn externals to pull the right versions into the
right places which works the same whether it is a manual checkout or a
jenkins build.
There shouldn't be anything 'new' on a slave unless jenkins builds it,
in which case you can archive the build artifacts as part of the job
so they end up versioned back on the master.
--
Les Mikesell
[email protected]
