Thanks. I see that you have migrated the job. https://ci-builds.apache.org/job/Ant/job/Ant%20Master%20(latest%20EA%20JDK)/
I placed some docs ... Jan -----Ursprüngliche Nachricht----- Von: Jaikiran Pai <[email protected]> Gesendet: Freitag, 14. August 2020 03:42 An: Ant Developers List <[email protected]>; [email protected] Betreff: Re: Migrating build jobs Hello Jan, On 13/08/20 3:32 pm, [email protected] wrote: > > > https://builds.apache.org/view/A/view/Ant/job/Ant%20Master%20(latest%2 > 0EA%20 > JDK)/ > > Ant Master (latest EA JDK) > > deactivated > > Last Success: 2m 22d > > Last Error: 25d > > > > Incomplete job. Tries to build on Java 1.5 + 1.6 (or 15+16?) > > Parameterized job with the download URL as parameter (without values) > > > > Shell: > > mkdir java-latest-ea > > cd java-latest-ea > > if [ "${jdk_axis}" == "jdk15-ea" ]; then > > wget ${JDK_15_DOWNLOAD_URL} > > else > > wget ${JDK_16_DOWNLOAD_URL} > > fi > > tar -zxf ./*.tar.gz > > # set JAVA_HOME to point to the newly extracted tar's content > > export JAVA_HOME=`echo \`pwd\`/\`echo */\`` > > echo "JAVA_HOME is set to $JAVA_HOME" > > export PATH=$JAVA_HOME/bin:$PATH > > cd .. > > java -version && ./build.sh -f fetch.xml -Ddest=optional && > ./bootstrap.sh && ./build.sh clean jars javadocs test > > > > > > Skipped this one as it seems that this job never had a real benefit. This is the job we use (and trigger manually) whenever the OpenJDK team contacts us (on the dev list) about new EA releases and asks us to try them out for catching any issues early in the JDK release cycle. I'll migrate this to the new CI since this has helped us catch and provide input to the OpenJDK team on newer JDK releases. -Jaikiran --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
