On Wed, Jan 16, 2013 at 3:00 PM, Les Mikesell <lesmikes...@gmail.com> wrote: > On Wed, Jan 16, 2013 at 3:25 AM, Guillaume Membré <gmem...@gmail.com> wrote: >> Hello, >> >> first of all, thanks a lot for the work you have done on jenkins, it is a >> fantastic piece of software ! >> >> I'm using jenkins 1.489 with 2 slaves. Many of my jobs run shell scripts, >> they are stored in eg JENKINS_HOME/jobs/job1/script1.sh. The job >> configuration to run this script is set to : "$WORKSPACE/../script1.sh" >> When running a build from the master, it runs ok, but from the slave, the >> script isn't copied to the slave workspace and thus the build failed. >> I would like to avoid a manual (or timed with cron) synchronisation between >> master and slaves. >> Is there an automatic way to synchronise such things between master and >> slaves ? Or, is there a way to know the master ip from a slave allowing the >> addition of a custom rsync before running script1.sh ? > > I think the usual approach is to put all of the build scripts into the > vcs (subversion/git, etc.) along with the source and let jenkins > check them out. That way they are versioned and always appear where > you need them.
thanks! I'll try both of your solutions and employ the one that works best for me!
