On Thu, Mar 28, 2013 at 1:56 PM, Scott Ellis <jackett_...@yahoo.com> wrote:
> Les,
>
> I appreciate the reply. I've been struggling with this still and would like
> to understand your setup better. It seems to me that you must have entries
> in your windows classpath that refers to mounted folders. So in my case, if
> I wanted to use groovy from a common location using your technique, you
> would modify the classpath of the slave node to refer to a groovy
> installation on the mounted drive.
>
> Do you modify the classpath then of the slave node in node settings?
No, as I said, I don't do it specifically with groovy myself and I'm
not sure if anyone even uses it with java jars. For things like boost
or running ant versions we use the jenkins envirornment/tool setup to
supply a \\host\path location on windows or a path to a configured nfs
mount location on linux. Windows has the complication that mapped
drive letters are specific to login sessions so you can't just map a
drive manually and expect jenkins to see the same location.
> Here is my specific problem, and an easy test to see if the problem is
> occurring:
>
> I have a local installation of groovy. I go to Jenkins->Manage
> Jenkins->Configure System
> In the Groovy section of the page, I click "Groovy installations..."
> I click Add Groovy, uncheck "Install Automatically", give this installation
> the name "Groovy 2.1.2", and specify my home folder
>
> Maybe this is where I could take advantage of your technique?! I'm on a Mac
> and the entire build is happening on this system. I have a single slave
> node and a master. How do I create a global reference to a location in
> linux that will work from the master or slave node?
I don't run any builds on the master, so I don't have to be concerned
about the location there. First you need to decide what to use as the
server for the shared directory. It doesn't have to be either of
the master or slave machines, and if it isn't you can simply nfs-mount
it into the same place on all targets so the same classpath will work.
If you do use the master as the file server you might need a symlink
to the real location to make the path look the same. I'd recommend a
read-only nfs export so you don't have to worry too much about
security issues - and then you just repeat the mount configuration on
any additional slaves you might add.
--
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/groups/opt_out.
