The machine which is trying to execute your ant.bat file probably does not
have the Ant bin directory in its path.  Since it can't find the ant.bat
file, it fails.  There are a few approaches you might consider:

- Modify the PATH on the Windows slave to include the Ant bin directory
(the location of ant.bat)
- Configure Jenkins to automatically install ant for you (global
configuration), then select that specific ant version in your job
- Start the Windows slave from a batch file that modifies the PATH to
include the Ant bin directory

Mark Waite


On Thu, May 1, 2014 at 7:42 PM, John Park <john.p...@sightlinesystems.com>wrote:

> Hi All,
>
> Glad this forum is around, I could sure use some help.  Here's my story:
>
> I have an ant script that's on the windows slave machine that I would like
> to run from the Jenkins browser, which is located on another server
> (master).  I followed the steps to set up a Master-Slave connection using
> the Java Web Start method, and that seemed to work, and saw that the
> Jenkins service was up and running.  I verified an established
> jenkins-service connection between the master and slave machines.  I have
> verified that the owner of the jenkins service belongs to the user that
> will kick off the ant script.  I have also verified from the browser that
> my slave windows node successfully is connected with Jenkins.  All looks
> well up to this point.
>
> I then created a new job on the browser with intentions of executing the
> ant script that resides on the slave.  I made sure to check the 'Restrict
> where this project can be run' box and added my slave node label. At this
> point, I thought that Jenkins would delegate this job to the slave
> everytime this job was executed.  I then proceeded to create a build step
> that would execute ant.bat from the slave, and saved the project.  The job
> kept failing, telling me that it could not find the path specified. I then
> realized that the job was probably searching for the directory in the
> master, and not the slave.  I looked around some more, but couldn't figure
> out how to configure the job properly in order for Jenkins to
> communicate/connect with the slave.
>
> Anything I might be missing here?
>
> Any help or advice is greatly appreciated.
>
> Thanks,
>
> JP
>
>
>  --
> 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.
>



-- 
Thanks!
Mark Waite

-- 
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.

Reply via email to