www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Bayer <andrew.ba...@gmail.com>
Subject Re: Apache Jenkins jobs unable to find "ant" (new issue)
Date Mon, 21 Jul 2014 22:44:14 GMT
I think that was a transient thing - I think Giri fixed the tools
paths, but I could be wrong.

A.

On Fri, Jul 18, 2014 at 1:32 PM, Patrick Hunt <phunt@apache.org> wrote:
> Ok, that's good to know.
>
> Perhaps to avoid confusion the "default" option (both the default and
> named default) should be removed then from the ant build step?
>
> Why was I previously able to call "ant" directly in a "execute shell"
> under build for the job, but now I can't? Is that expected?
>
> Thanks!
>
> Patrick
>
> On Fri, Jul 18, 2014 at 1:21 PM, Andrew Bayer <andrew.bayer@gmail.com> wrote:
>> You've got to choose a specific version of Ant when you're using the
>> Ant build step - I've updated the job.
>>
>> On Fri, Jul 18, 2014 at 11:06 AM, Patrick Hunt <phunt@apache.org> wrote:
>>> Hi. This job was running fine until just recently
>>>
>>> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-jdk7/916/console
>>>
>>> It used to have a bash command running ant to do the build. It started
>>> failing recently (unable to find ant). So I updated the configuration
>>> to use the "ant" build command in the jenkins job rather than using
>>> bash. However the same issue exists.
>>>
>>> Please take a look at the output of that job, near the bottom you'll
>>> see the issue.
>>>
>>> Thanks,
>>>
>>> Patrick

Mime
View raw message