infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Drew Foulks (JIRA)" <>
Subject [jira] [Commented] (INFRA-18367) Latest version of Ant not being picked up by Jenkins build
Date Fri, 17 May 2019 13:40:00 GMT


Drew Foulks commented on INFRA-18367:

/boot was full so I cleaned up a few old kernels that were causing the host to fail puppet
runs. In turn, this fixed the ANT issue you were seeing. Latest is now symbolically linked
to Ant (1.10.6 latest1.10 -> /usr/local/asfpackages/ant/apache-ant-1.10.6).

Please re-run the job and let me know how it goes.

> Latest version of Ant not being picked up by Jenkins build
> ----------------------------------------------------------
>                 Key: INFRA-18367
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Rick Hillegas
>            Assignee: Drew Foulks
>            Priority: Major
> The Derby build/test cycle fails after having updated its Ant build script to require
the latest and newly released version of Ant (1.10.6). The Jenkins configurations for Derby
builds specify that the latest version of Ant should be used. But the build fails with the
following message:
> {noformat}
> <>:95: FATAL ERROR:
 The running Ant version, 1.10.5, is too old.
> {noformat}
> It appears that Jenkins still thinks that the latest version of Ant is 1.10.5.
> See, for instance,
> Can you update Jenkins to understand that there is a new Ant version?
> Thanks,
> -Rick

This message was sent by Atlassian JIRA

View raw message