On Tue, Jul 31, 2012 at 2:41 PM, David Weintraub <[email protected]> wrote:
>
> Are you building everything on the jenkins host? Why not do builds
>> on slaves (even on the same host if necessary), and tell jenkins to
>> archive the build artifacts you want? Then you can mount the NAS
>> storage wherever jenkins puts the artifacts without affecting builds -
>> or requiring the normally disposable workspaces to be on the NAS.
>
> Unfortunately, I don't have any slaves now. However, I never knew I
> could have the machine itself as a slave. Interesting idea...
Jenkins doesn't particularly care where a slave runs as long as you
can get it connected (and ssh is easy).
> However, it looks like there are two fairly new Jenkins options that
> do what I would want. I can specify where to put the working directory
> or the build storage separate from the jobs directory. If that doesn't
> work, I'll do the slave setup.
As long as you are archiving what you want to keep and not using the
workspaces directly it probably doesn't matter.
--
Les Mikesell
[email protected]
