remote builds in recent Hudson

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

remote builds in recent Hudson

Vladimir Sizikov
Hi,

I switched to the latest Hudson 1.72, and trying to update my remote
jobs so that they could be run with the latest Hudson remoting
infrastructure.

So far, the main problem is that subversion is not in the path for
remote machines (the machines are Solaris boxes and have subversion
installed in non-default location, and I have no rights to modify
system places like /bin or /usr/bin).

So, basically, I have 3 different systems with three different paths
to subversion.

What is an official way of dealing with such problems?
Is there a way to specify (or update) PATH for slaves?

Thanks,
  --Vladimir

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: remote builds in recent Hudson

Kohsuke Kawaguchi-2
Vladimir Sizikov wrote:

> Hi,
>
> I switched to the latest Hudson 1.72, and trying to update my remote
> jobs so that they could be run with the latest Hudson remoting
> infrastructure.
>
> So far, the main problem is that subversion is not in the path for
> remote machines (the machines are Solaris boxes and have subversion
> installed in non-default location, and I have no rights to modify
> system places like /bin or /usr/bin).
>
> So, basically, I have 3 different systems with three different paths
> to subversion.
>
> What is an official way of dealing with such problems?
> Is there a way to specify (or update) PATH for slaves?
I do this by writing a wrapper script to launch slave.jar. See
https://hudson.dev.java.net/masterSlave.html

Another approach I use for dealing with machine-specificness like this
is to create /home/hudson/bin, put that in PATH, and put symlinks to the
actual location.

We could let the path of various things (like SVN executable, JDK HOME,
etc) to be overrided in individual slaves, I guess. Doing this without
cluttering UI needs some thinking, but there's an appeal in being able
to do everything from the UI.

Also, if we want to do ad-hoc griding, it's a must that slaves can
specify their own path of everything.

>
> Thanks,
>   --Vladimir
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment