On Fri, Feb 7, 2014 at 11:30 AM, Baptiste Mathus wrote:
> But, I'll add, better don't do it.
>
> Let Jenkins install ant by himself on the slaves. It will really make your
> life simpler. If the public ant versions don't suit your needs, you can even
> just package the one you need, upload it some
I did switch and let Jenkins configure it and it does work great. The issue I
have now is that when I run the build.xml through Jenkins on the slave, it
does not read the properties from the environment using:
If I run it manually from a cmd windows on the server it does. Seems to be the
But, I'll add, better don't do it.
Let Jenkins install ant by himself on the slaves. It will really make your
life simpler. If the public ant versions don't suit your needs, you can
even just package the one you need, upload it somewhere in your company and
tell Jenkins to install this version ins
On Thu, Feb 6, 2014 at 3:11 PM, Mark Waite wrote:
> The easiest way with Ant is to use the Jenkins global configuration to
> configure an Ant installation, and have it download that Ant installation
> from Apache. Then you define the job to use the specific Ant version you
> configured, and it wi
The easiest way with Ant is to use the Jenkins global configuration to
configure an Ant installation, and have it download that Ant installation
from Apache. Then you define the job to use the specific Ant version you
configured, and it will be downloaded and used for that build.
That keeps your
I have set up a new slave and it needs to run ANT. I have downloaded and
installed. Set ANT_HOME and the PATH. I can run from the cmd prompt. I
stopped the Jenkins java process and restarted it on the slave, but when I run
the job I keep getting:
$ cmd.exe /C '"ant.bat -file build.xml
-Dco
