On Thu, Feb 21, 2013 at 8:20 PM, <[email protected]> wrote:
>
> The desired effect is
>
> d:\jenkinsslave\slave.jar ....
> d:\wp\job1 ...
>
> Instead of
>
> d:\jenkinsslave\slave.jar ....
> \workspace\job1 ...
>
You can have d:\wp\workspace\job1 with the slave jar residing in
d:\wp. I'd guess that any other layout would require code changes.
But in general I think it is best to not rely on anything permanent
regarding any individual slave or it's file storage. That is, move
anything you want to keep permanently to it's desired location either
with commands in your build script, or letting the master archive it,
or with one of the publishing plugins. Among other things, that can
let you use common network storage and easily scale up the slave pool
or handle individual slave failures.
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
