There is none installed and I actually don't want to manually install one
as Jenkins has an auto-install facility. So I do not see any other solution
than specifying ANT 1.9 in the job, as obviously Jenkins does not have a
I don't care, just install any feature.
Am Mittwoch, 23. Oktober 2013
It would be great if there would simply be a Standard: [ANT 1.9]
selection box in Jenkins' ANT installations section, so I could avoid
manually installing it! :-)
Am Dienstag, 22. Oktober 2013 16:08:01 UTC+2 schrieb Daniel Beck:
I used the tool whose version is least significant in most of my
On Wed, Oct 23, 2013 at 1:51 AM, k...@quipsy.de wrote:
It would be great if there would simply be a Standard: [ANT 1.9] selection
box in Jenkins' ANT installations section, so I could avoid manually
installing it! :-)
I think standard means 'the one you already have and use' not 'pick
Are you sure you are talking about ANT? It sounds like you talk about JDK.
Am Freitag, 18. Oktober 2013 18:55:22 UTC+2 schrieb Daniel Beck:
The 'default' tool version uses whatever is the preferred version on the
node's PATH. In this case, there is none.
This can be useful when you don't
In my particular case, the ANT script to run is so ridiculously simple that
it won't fail ever. It consists only of a single exec. So I'd be happy if
I could just tell Jenkins that it shall just pick any ANT to do the job.
Am Montag, 21. Oktober 2013 11:39:52 UTC+2 schrieb Andreas Schilling:
On Tue, Oct 22, 2013 at 5:26 AM, k...@quipsy.de wrote:
In my particular case, the ANT script to run is so ridiculously simple that
it won't fail ever. It consists only of a single exec. So I'd be happy if
I could just tell Jenkins that it shall just pick any ANT to do the job.
Is there an
No, it is not. I want Jenkins to install ANT and then use that one, which
works fine if I specify an explicit ANT version in the job. But I don't
care that the exact version, as the job in fact would run with really any
version of ANT.
Am Dienstag, 22. Oktober 2013 14:53:12 UTC+2 schrieb
I used the tool whose version is least significant in most of my jobs as
example, but as you're facing the exact same situation with Ant, it applies as
well.
That's basically the use case: You install Ant system-wide (e.g. from your
Linux distro's repository), it's put into your PATH (possibly
Hi Markus,
while I understand your point of view (thought the same some time ago) I
nowadays highly recommend to use explicit tool versions for everything. My
experience is that it is alot easier to track down build problems if
explicit versions are used everywhere. It may be a hassle to
I have installed Jenkins 1.514 and told it to automatically provide solely
ANT 1.9.2 from Apache. So there is only ANT 1.9.2 on Master and no other
ANT installation.
Then I created a project with the Run Ant build task and explicitly
specified to use ANT 1.9.2 in the ANT version configuration
The 'default' tool version uses whatever is the preferred version on the node's
PATH. In this case, there is none.
This can be useful when you don't care about the Java version used in a job,
and have the executing node use its default installation without having to
configure the path for
11 matches
Mail list logo
