On Thu, Oct 16, 2014 at 9:46 AM, Niksan <sumot...@googlemail.com> wrote:
> Oddly enough, if I set custom workspace and remote root both to C:\Chk this
> works as intended, but that limits one job per node. :/
>
No, if you run other jobs on that node they should be created as
C:\Chk\jobname\.
But that's probably not what you want, so use some other remote root
and specify the custom workspace for just this job. Unless you are
doing something with a very special reason to only exist on this one
node at that location, I'd recommend thinking about ways to make it
run in a normal workspace, though. It is generally easier to manage
jenkins when you can set up pools of slaves with identifying labels
and have jobs that can run on any node with a matching label. If a job
is set up to find anything it needs from a source checkout, UNC paths,
etc., and archive its results back to the master you don't have to do
anything special to replace a slave node. There are special cases, of
course, where you can't do that...
--
Les Mikesell
lesmikes...@gmail.com
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
