On Fri, May 2, 2014 at 9:25 AM, John Park
<john.p...@sightlinesystems.com> wrote:
> To be honest, I have never tried invoking ant from the build step in
> jenkins..I just took a look at it, but I don't see how this would be more
> beneficial (or easier) for me, since I have everything already set up on the
> slave machine...all I should be doing is executing an ant command to run the
> script.
>
> Is there some benefit to invoking ant in jenkins vs executing it from the
> slave?
I don't think you understand. Invoking ant in jenkins will execute it
on the slave where the job runs. But it also lets you set the version
and location for ant (and the jdk to use) in a high-level way. That
is, you can give the versions a name in the global jenkins config, and
set (potentially different) locations for the tools in each node
config. And you can pick the versions in your job file (if there are 2
or more). Then, even if ant and the jdk(s) are installed in
different locations on your own workstation, you can tell jenkins to
run the same ant job from the SCM and it will work regardless of which
node runs it.
--
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/d/optout.
