Silly question, does the build.xml that's on the slave have to be on the master machine's root workspace directory in order for it to run on the slave?
I made changes to the node configuration based on your pointers, and re-ran the project. On this try, I gave an explicit path to the build file, then got this message: Started by upstream project "master_slave_test" build number 51 originally caused by: Started by user John Park [EnvInject] - Loading node environment variables. Building on master in workspace < http://build:80/job/master_slave_test/default/ws/<http://build/job/EDM_deploy_on_dorado/default/ws/> > FATAL: Unable to find build script at < http://build:80/job/master_slave_test/default/ws/build.xml<http://build/job/EDM_deploy_on_dorado/default/ws/build.xml> / <http://build/job/EDM_deploy_on_dorado/default/ws/>"C>:\Builds\build.xml" Build step 'Invoke Ant' marked build as failure Seems like there's a syntax error based on the above message, as it looks to close the C: drive within the URL tag. I then moved the build file to the jennkins/ directory on the slave machine and re-ran, but got the same message: Started by upstream project "master_slave_test" build number 53 originally caused by: Started by user John Park [EnvInject] - Loading node environment variables. Building on master in workspace <http://build:80/job/master_slave_test /default/ws/ <http://build/job/EDM_deploy_on_dorado/default/ws/>> FATAL: Unable to find build script at <http://build:80/job/master_slave_test /default/ws/build.xml<http://build/job/EDM_deploy_on_dorado/default/ws/build.xml> > Build step 'Invoke Ant' marked build as failure Some other potential useful info: The path I gave to ant home and java home when configuring globally was only to the apache ant and jdk folders, i did not include bin in the path Same goes for configuring the path in the nodes config. Based on the error message, the job seems to be executing from the master, and not the slave. Thanks, -John P. On Fri, May 2, 2014 at 12:09 PM, Les Mikesell <lesmikes...@gmail.com> wrote: > On Fri, May 2, 2014 at 10:56 AM, John Park > <john.p...@sightlinesystems.com> wrote: > > Hi Les, > > > > OK, I think I get what you're saying, so this is what I did: > > > > I set ant and java globally in jenkins and pointed java home and ant > home to > > directories on the jenkins machine (master) > > > > I then added those global settings to my slave node. > > On the slave node config, the path should be to the location on that > slave. At least if it is different from the global entry. > > > I then added a build step to invoke ant, added the global ant setting, > added > > which target i wanted to run, included the path to the build.xml on the > > slave machine. > > > > I ran the job, but it still failed incidcating that it could not find the > > specified path to the build.xml.. > > It expects build.xml to be in the root of the (usually checked-out > from SCM) workspace. Or you can give an explict path if it is > elsewhere for some reason. > > > I'm convinced that Jenkins (master) is not properly delegating my job to > the > > slave machine...to test this, I had ant execute a simple test batch file > i > > created to echo "hello world" from the slave, but I got a message saying > > that it didn't recognize tha batch file...I then tested this locally > from a > > command prompt on the jenkins server, where the .bat doesn't exist, and > got > > the same message. > > You should see which node ran a job over at the top left of the build # > page. > > > Again, thanks for the input and advice, but I think the root of my > problem > > here is getting the master to properly delagate control to the slave > > machine. > > That is controlled by the 'restrict where job can run' item in the job > config. You can use nodenames or labels there. It is a good idea to > always give the nodes labels according to their capabilities and > restrict jobs to labels since that makes it easy to add more nodes for > certain build types as the load increases or to fail over as slaves > are down/replaced. > > -- > Les Mikesell > lesmikes...@gmail.com > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/0ELSkd80t_Q/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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.
