Re: Deprecated JDKs being removed from Jenkins soon.
Thanks. Another example we saw recently: https://builds.apache.org/job/kafka-pr-jdk9-scala2.12/1524/console Ismael On Sun, Sep 24, 2017 at 11:06 AM, Gavin McDonald wrote: > > > On 24 Sep 2017, at 6:52 pm, Ismael Juma wrote: > > > > Thanks for the quick response. Seems like it was H25: > > Thanks. > > So a regression in openjdk-9-jdk (b118) caused the node to not update from > puppet > any more, so the install and link for latest1.9 did not happen. > > Fixed, thanks for reporting. > > Gav… > > > > > https://builds.apache.org/job/kafka-trunk-jdk9/57/ > > > > Ismael > > > > On Sun, Sep 24, 2017 at 9:19 AM, Gavin McDonald > > wrote: > > > >> > >>> On 24 Sep 2017, at 5:47 pm, Ismael Juma wrote: > >>> > >>> Hi Gavin, > >>> > >>> To avoid running into problems when 9-b181 is removed, I changed Apache > >>> Kafka's Jenkins jobs to use JDK 1.9 (latest) (which is what we do for > >> Java > >>> 7 and Java 8) and got: > >>> > >>> ERROR: JAVA_HOME is set to an invalid directory: > >>> /home/jenkins/tools/java/latest1.9 > >>> > >>> > >>> Is the roll out of the final JDK 9 still in progress? > >> > >> I spot checked on a few Jenkins slaves, can you tell me which one you > >> failed on? > >> > >> Thanks > >> > >> Gav… > >> > >> > >> gmcdonald@asf927:~$ /home/jenkins/tools/java/latest1.9/bin/java > -version > >> java version "9" > >> Java(TM) SE Runtime Environment (build 9+181) > >> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) > >> > >> gmcdonald@asf914:~$ /home/jenkins/tools/java/latest1.9/bin/java > -version > >> java version "9" > >> Java(TM) SE Runtime Environment (build 9+181) > >> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) > >> > >> gmcdonald@asf910:~$ /home/jenkins/tools/java/latest1.9/bin/java > -version > >> java version "9" > >> Java(TM) SE Runtime Environment (build 9+181) > >> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) > >> > >> gmcdonald@asf900:~$ /home/jenkins/tools/java/latest1.9/bin/java > -version > >> java version "9" > >> Java(TM) SE Runtime Environment (build 9+181) > >> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) > >> > >> > >>> > >>> Thanks, > >>> Ismael > >>> > >>> On Sun, Sep 24, 2017 at 8:10 AM, Gavin McDonald < > ga...@16degrees.com.au> > >>> wrote: > >>> > Hi All, > > As advertised on https://cwiki.apache.org/ > confluence/display/INFRA/JDK+ > Installation+Matrix , we will > be removing some older JDK releases from Jenkins. > > 1.8.0_92, 1.8.0_102, 9-b128, 9-b132, 9-b139, 9-b142 will all be > removed > within the next few days. > > Should your builds be using any of these, please migrate to a later > version of JDK 1.8 or 9. > > Thanks > > Gav… (ASF Infra Team) > > > >> > >> > >
Re: Deprecated JDKs being removed from Jenkins soon.
> On 29 Sep 2017, at 10:13 am, Ismael Juma wrote: > > Thanks. Another example we saw recently: > > https://builds.apache.org/job/kafka-pr-jdk9-scala2.12/1524/console > Thanks, fixed that node too. Will check for others. Gav… > Ismael > > On Sun, Sep 24, 2017 at 11:06 AM, Gavin McDonald > wrote: > >> >>> On 24 Sep 2017, at 6:52 pm, Ismael Juma wrote: >>> >>> Thanks for the quick response. Seems like it was H25: >> >> Thanks. >> >> So a regression in openjdk-9-jdk (b118) caused the node to not update from >> puppet >> any more, so the install and link for latest1.9 did not happen. >> >> Fixed, thanks for reporting. >> >> Gav… >> >>> >>> https://builds.apache.org/job/kafka-trunk-jdk9/57/ >>> >>> Ismael >>> >>> On Sun, Sep 24, 2017 at 9:19 AM, Gavin McDonald >>> wrote: >>> > On 24 Sep 2017, at 5:47 pm, Ismael Juma wrote: > > Hi Gavin, > > To avoid running into problems when 9-b181 is removed, I changed Apache > Kafka's Jenkins jobs to use JDK 1.9 (latest) (which is what we do for Java > 7 and Java 8) and got: > > ERROR: JAVA_HOME is set to an invalid directory: > /home/jenkins/tools/java/latest1.9 > > > Is the roll out of the final JDK 9 still in progress? I spot checked on a few Jenkins slaves, can you tell me which one you failed on? Thanks Gav… gmcdonald@asf927:~$ /home/jenkins/tools/java/latest1.9/bin/java >> -version java version "9" Java(TM) SE Runtime Environment (build 9+181) Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) gmcdonald@asf914:~$ /home/jenkins/tools/java/latest1.9/bin/java >> -version java version "9" Java(TM) SE Runtime Environment (build 9+181) Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) gmcdonald@asf910:~$ /home/jenkins/tools/java/latest1.9/bin/java >> -version java version "9" Java(TM) SE Runtime Environment (build 9+181) Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) gmcdonald@asf900:~$ /home/jenkins/tools/java/latest1.9/bin/java >> -version java version "9" Java(TM) SE Runtime Environment (build 9+181) Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) > > Thanks, > Ismael > > On Sun, Sep 24, 2017 at 8:10 AM, Gavin McDonald < >> ga...@16degrees.com.au> > wrote: > >> Hi All, >> >> As advertised on https://cwiki.apache.org/ >> confluence/display/INFRA/JDK+ >> Installation+Matrix , we will >> be removing some older JDK releases from Jenkins. >> >> 1.8.0_92, 1.8.0_102, 9-b128, 9-b132, 9-b139, 9-b142 will all be >> removed >> within the next few days. >> >> Should your builds be using any of these, please migrate to a later >> version of JDK 1.8 or 9. >> >> Thanks >> >> Gav… (ASF Infra Team) >> >> >> >>
Re: Deprecated JDKs being removed from Jenkins soon.
Thanks! Ismael On Fri, Sep 29, 2017 at 1:45 AM, Gavin McDonald wrote: > > > On 29 Sep 2017, at 10:13 am, Ismael Juma wrote: > > > > Thanks. Another example we saw recently: > > > > https://builds.apache.org/job/kafka-pr-jdk9-scala2.12/1524/console > > > > Thanks, fixed that node too. > > Will check for others. > > Gav… > > > Ismael > > > > On Sun, Sep 24, 2017 at 11:06 AM, Gavin McDonald > > > wrote: > > > >> > >>> On 24 Sep 2017, at 6:52 pm, Ismael Juma wrote: > >>> > >>> Thanks for the quick response. Seems like it was H25: > >> > >> Thanks. > >> > >> So a regression in openjdk-9-jdk (b118) caused the node to not update > from > >> puppet > >> any more, so the install and link for latest1.9 did not happen. > >> > >> Fixed, thanks for reporting. > >> > >> Gav… > >> > >>> > >>> https://builds.apache.org/job/kafka-trunk-jdk9/57/ > >>> > >>> Ismael > >>> > >>> On Sun, Sep 24, 2017 at 9:19 AM, Gavin McDonald < > ga...@16degrees.com.au> > >>> wrote: > >>> > > > On 24 Sep 2017, at 5:47 pm, Ismael Juma wrote: > > > > Hi Gavin, > > > > To avoid running into problems when 9-b181 is removed, I changed > Apache > > Kafka's Jenkins jobs to use JDK 1.9 (latest) (which is what we do for > Java > > 7 and Java 8) and got: > > > > ERROR: JAVA_HOME is set to an invalid directory: > > /home/jenkins/tools/java/latest1.9 > > > > > > Is the roll out of the final JDK 9 still in progress? > > I spot checked on a few Jenkins slaves, can you tell me which one you > failed on? > > Thanks > > Gav… > > > gmcdonald@asf927:~$ /home/jenkins/tools/java/latest1.9/bin/java > >> -version > java version "9" > Java(TM) SE Runtime Environment (build 9+181) > Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) > > gmcdonald@asf914:~$ /home/jenkins/tools/java/latest1.9/bin/java > >> -version > java version "9" > Java(TM) SE Runtime Environment (build 9+181) > Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) > > gmcdonald@asf910:~$ /home/jenkins/tools/java/latest1.9/bin/java > >> -version > java version "9" > Java(TM) SE Runtime Environment (build 9+181) > Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) > > gmcdonald@asf900:~$ /home/jenkins/tools/java/latest1.9/bin/java > >> -version > java version "9" > Java(TM) SE Runtime Environment (build 9+181) > Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) > > > > > > Thanks, > > Ismael > > > > On Sun, Sep 24, 2017 at 8:10 AM, Gavin McDonald < > >> ga...@16degrees.com.au> > > wrote: > > > >> Hi All, > >> > >> As advertised on https://cwiki.apache.org/ > >> confluence/display/INFRA/JDK+ > >> Installation+Matrix , we will > >> be removing some older JDK releases from Jenkins. > >> > >> 1.8.0_92, 1.8.0_102, 9-b128, 9-b132, 9-b139, 9-b142 will all be > >> removed > >> within the next few days. > >> > >> Should your builds be using any of these, please migrate to a later > >> version of JDK 1.8 or 9. > >> > >> Thanks > >> > >> Gav… (ASF Infra Team) > >> > >> > > > >> > >> > >
Re: Jenkins Github PR integration - Support for whitelisting?
On 2017-09-27 23:26, Meghna Baijal wrote: Thanks Dominik! I looked at Log4net’s Jenkinsfile and it is going to be a good reference for me in the future. I am currently adding some features via the Jenkinsfile script and I am hoping they will work as expected on Apache Jenkins :) Thanks for the Kudos. Please note that the pipeline is not finished at all and lacks several important stages like publishing the generated site and built binaries on release branches and tags. In case you can make this work I would like to see how you made that work. Would you please ping here or d...@logging.apache.org when you've finished that? Please note further that we observed some strange things with log4net's build job. One is that the job at the end reports "Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected". I assume that the github plugin would like to save a build status on the commit but is unable to do so because of a credential issue. I'm sure that I've granted repo:status on the credentials that jenkins uses and it is most likely because my github user is part of the apache organization but only the apache organization can save such changes. Does anyone know whether this is the case or not?
