db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendleton.de...@gmail.com>
Subject Re: Ant version in Jenkins
Date Sun, 06 May 2018 16:00:38 GMT
When I look here:

https://cwiki.apache.org/confluence/display/INFRA/Ant+Installation+Matrix

it seems to be saying that the newest version of Ant that is installed
on the Jenkins slaves is 1.10.1.

I see on ant.apache.org that the Ant team have now released 1.10.3.

I'll see if I can figure out where to ask Infra for an upgrade.

thanks,

bryan


On Sun, May 6, 2018 at 7:22 AM, Rick Hillegas <rick.hillegas@gmail.com> wrote:
> On 5/5/18 6:31 PM, Bryan Pendleton wrote:
>>
>> Rick, we require Ant version 1.10.2 now?
>
> I did not make that change to Jenkins. We seem to be running with 1.10.1.
>>
>>
>> How do we update the version of Ant that is installed on
>> on the Jenkins servers?
>
> I'm afraid that I know very little about Jenkins. This is why I have not
> touched it. At some point in the past I tried unsuccessfully to update the
> Jenkins builds. I don't remember what I did and failed to accomplish.
>
> I don't see anything useful when I go to the build page at
> https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/
>
> If I click on a build, I get a screen with some hopeful looking links on the
> left. See
> https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/lastBuild/
>
> Somewhere there is a screen which lets you define the script which the build
> runs. I think that screen lets you define the version level of the tools
> needed by the script. But I can't find that script now.
>
> Maybe the links I am looking for are hidden because I haven't clicked on the
> "log in" link in the upper right corner and logged in. However, I have
> searched through my password vault and I have no record of credentials
> created for Jenkins.
>
> I wouldn't mind doing some light maintenance on our Jenkins setup if I
> understood it. But I haven't found the time to read all the Jenkins
> documentation and figure this stuff out. Maybe there is a short primer on
> our wiki explaining how to maintain Jenkins. I can't find it.
>
> I would not mind turning off the Jenkins machinery if it is providing no
> value and no-one knows how to maintain it. Maybe the exercise of turning
> Jenkins off would teach us enough to maintain it.
>
> Sorry that I don't have anything useful to say.
>
> -Rick
>
>>
>> thanks,
>>
>> bryan
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Apache Jenkins Server <jenkins@builds.apache.org>
>> Date: Sat, May 5, 2018 at 4:37 PM
>> Subject: Build failed in Jenkins: Derby-trunk-suites.All #165
>> To: derby-dev@db.apache.org, rhillegas@apache.org, bpapache5@geekdom.net
>>
>>
>> See
>> <https://builds.apache.org/job/Derby-trunk-suites.All/165/display/redirect?page=changes>
>>
>> Changes:
>>
>> [bpendleton] DERBY-6988: Update STATUS page for 10.14.2.0
>>
>> [bpendleton] DERBY-6988: Add 10.14.2.0 to versions table
>>
>> [bpendleton] DERBY-6988: Checkin 10.14.2.0 jars for upgrade testing
>>
>> [rhillegas] DERBY-6945: Add a ResourceBundleProvider for the client
>> messages so that they can be found when Derby is run using a
>> modulepath; commit
>> derby-6945-31-aa-clientmessages-ResourceBundleProvider.diff.
>>
>> ------------------------------------------
>> Started by an SCM change
>> [EnvInject] - Loading node environment variables.
>> Building remotely on H30 (ubuntu xenial) in workspace
>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/>
>> Updating https://svn.apache.org/repos/asf/db/derby/code/trunk at
>> revision '2018-05-05T23:37:06.309 +0000'
>> U
>> java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/OldVersions.java
>> U         java/client/module-info.java
>> A         java/client/org/apache/derby/loc
>> A         java/client/org/apache/derby/loc/client
>> AU
>> java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyTesting.jar.lastcontents
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyclient.jar.lastcontents
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbytools.jar.lastcontents
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyTesting.jar.lastcontents
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyclient.jar.lastcontents
>> A         java/shared/org/apache/derby/loc
>> A         java/shared/org/apache/derby/loc/client
>> A         java/shared/org/apache/derby/loc/client/spi
>> AU
>> java/shared/org/apache/derby/loc/client/spi/clientmessagesProvider.java
>> U         java/shared/module-info.java
>> U         STATUS
>>   U        .
>> At revision 1831011
>>
>> Updating https://svn.apache.org/repos/asf/db/derby/jars at revision
>> '2018-05-05T23:37:06.309 +0000'
>> A         10.14.2.0
>> AU        10.14.2.0/derbyLocale_pl.jar
>> AU        10.14.2.0/derbyLocale_it.jar
>> AU        10.14.2.0/derbyLocale_hu.jar
>> AU        10.14.2.0/derby.war
>> AU        10.14.2.0/derbytools.jar
>> AU        10.14.2.0/derbyLocale_ja_JP.jar
>> AU        10.14.2.0/derbyrun.jar
>> AU        10.14.2.0/derbyLocale_ru.jar
>> AU        10.14.2.0/derbyoptionaltools.jar
>> AU        10.14.2.0/derbyLocale_zh_TW.jar
>> AU        10.14.2.0/derbyTesting.jar
>> AU        10.14.2.0/derbyclient.jar
>> AU        10.14.2.0/derby.jar
>> AU        10.14.2.0/derbyLocale_de_DE.jar
>> AU        10.14.2.0/derbyLocale_zh_CN.jar
>> AU        10.14.2.0/derbyLocale_cs.jar
>> AU        10.14.2.0/derbyLocale_ko_KR.jar
>> AU        10.14.2.0/derbyLocale_pt_BR.jar
>> AU        10.14.2.0/derbynet.jar
>> AU        10.14.2.0/derbyLocale_es.jar
>> AU        10.14.2.0/derbyLocale_fr.jar
>> At revision 1831011
>>
>> [locks-and-latches] Checking to see if we really have the locks
>> [locks-and-latches] Have all the locks, build can start
>> [Derby-trunk-suites.All] $ /bin/bash -xe
>> /tmp/jenkins2993569736394132251.sh
>> + rm -Rf 'trunk/junit_*'
>> [trunk] $ /home/jenkins/tools/ant/latest/bin/ant clobber all
>> buildjarsclean
>> Buildfile:
>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>
>>
>> clean:
>>
>> cleangenerated:
>>
>> cleanstate:
>>
>> cleanreleasefiles:
>>
>> clobber:
>>
>> checkCompilerLevel:
>>
>> version_check:
>>
>> BUILD FAILED
>>
>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>:66:
>> FATAL ERROR:  The running Ant version, 1.10.1, is too old.
>>
>> Total time: 0 seconds
>> Build step 'Invoke Ant' marked build as failure
>> [locks-and-latches] Releasing all the locks
>> [locks-and-latches] All the locks released
>> Recording test results
>> ERROR: Step ?Publish JUnit test result report? failed: No test report
>> files were found. Configuration error?
>>
>

Mime
View raw message