[aside]There we have a perfect example of somebody presuming there is a lot of work to do and going and doing half of it up front[/aside]
Jenkins has this lovely tool auto installation feature. You just tell Jenkins the Maven versions you need and ask it to do the downloading from the Apache web site and... presto... all the slaves will get that version of Maven and you don;t need to worry about paths at all -Stephen On 14 December 2012 16:53, Z W <mpc8...@gmail.com> wrote: > Hi > > We downloaded Maven 3.0.4 binary from the apache web site. > We have a distributed network where Jenkins is in one linux box A with > 2 slaves on the other 2 linux boxes, named B and C. > We untar the maven file in box A and configured Jenkins to NOT install > automatically and point maven home in /path/to/maven/home > We saw that the slaves each already has maven > > [root@B bundled-maven]# pwd > /slave/path/to/maven/slavebundle/bundled-maven > [root@B bundled-maven]# cd .. > [root@B slavebundle]# ls > bundled-maven lib resources > [root@B slavebundle]# ls -lrt > total 12 > drwxr-xr-x 2 root root 4096 Nov 21 17:44 resources > drwxr-xr-x 6 root root 4096 Nov 21 17:44 bundled-maven > drwxr-xr-x 2 root root 4096 Nov 21 17:44 lib > [root@B slavebundle]# ls -lrt resources/ > total 4 > -rw-r--r-- 1 root root 2306 Dec 6 2011 logback.xml > [root@B slavebundle]# ls -lrt lib > total 724 > -rw-r--r-- 1 root root 53889 Dec 6 2011 maven3-eventspy-3.0.jar > -rw-r--r-- 1 root root 680009 Dec 6 2011 maven3-eventspy-runtime.jar > [root@B slavebundle]# ls -lrt bundled-maven/ > total 36 > -rw-r--r-- 1 root root 2559 Feb 28 2011 README.txt > -rw-r--r-- 1 root root 1030 Feb 28 2011 NOTICE.txt > -rw-r--r-- 1 root root 11560 Feb 28 2011 LICENSE.txt > drwxr-xr-x 2 root root 4096 Nov 21 17:44 boot > drwxr-xr-x 2 root root 4096 Nov 21 17:44 bin > drwxr-xr-x 2 root root 4096 Nov 21 17:44 conf > drwxr-xr-x 3 root root 4096 Nov 21 17:44 lib > [root@B slavebundle]# pwd > /slave/path/to/maven/slavebundle > [root@B slavebundle]# > > 1- Must we install our new Maven on each of the slaves separately ? > 2- How do we force Jenkins to new the new Maven on the slaves and > Jenkins box A ? > 3- What must we configure in Manage Jenkins Maven 3 section to make > sure that all the boxes are using the same Maven 3.0.4 ? > 4- Must we copy ourselves manually to the slaves in > /slave/path/to/maven/slavebundle and remove the older ones ? > > Thanks >
