On 07/12/2014, at 8:53 PM, Andrew Bayer <[email protected]> wrote:
> Ah, gotcha. I'll take a look and see if there's a maintainable way to > handle this… In the meantime, can we still have a jira BUILDS ticket so we can track its progress and the cure etc ? Thanks Gav… > On Dec 7, 2014 12:52 PM, "Steve Loughran" <[email protected]> wrote: > >> On 7 December 2014 at 20:42, Andrew Bayer <[email protected]> wrote: >> >>> Actually, it is by design - we'd like to avoid having to manually install >>> JVMs on every slave when possible. The auto-installing JDKs from the drop >>> down are the preferred way to handle this - if you need a new JDK added >>> there, open a BUILDS ticket. >>> >>> >> fine, but you aren't answer the question >> >> why does the link to "latest" not point to the latest JDK on the target >> machines. >> >> That's not a versioning problem, it's a path maintenance problem >> >> >>> A. >>> On Dec 7, 2014 10:09 AM, "Gavin McDonald" <[email protected]> >> wrote: >>> >>>> >>>> On 07/12/2014, at 3:49 PM, Steve Loughran <[email protected]> >>> wrote: >>>> >>>>> while dealing with some fun moving hadoop-patch-test Jenkins to java >> 7, >>>> one >>>>> thing that I can see is that the symlinks of latests java versions >>> aren't >>>>> >>>>> lrwxrwxrwx 1 jenkins jenkins 39 Oct 6 22:40 latest -> >>>>> /home/jenkins/tools/java/jdk1.6.0_45-64 >>>>> lrwxrwxrwx 1 jenkins jenkins 13 Jul 23 2011 latest1.4 -> >>>> j2sdk1.4.2_19 >>>>> lrwxrwxrwx 1 jenkins jenkins 14 Jul 23 2011 latest1.5 -> >>>> jdk1.5.0_22-32 >>>>> lrwxrwxrwx 1 jenkins jenkins 14 Jul 23 2011 latest1.5-32 -> >>>>> jdk1.5.0_22-32 >>>>> lrwxrwxrwx 1 jenkins jenkins 14 Jul 23 2011 latest1.5-64 -> >>>>> jdk1.5.0_22-64 >>>>> lrwxrwxrwx 1 jenkins jenkins 14 May 14 2013 latest1.6 -> >>>> jdk1.6.0_45-32 >>>>> lrwxrwxrwx 1 jenkins jenkins 14 May 14 2013 latest1.6-32 -> >>>>> jdk1.6.0_45-32 >>>>> lrwxrwxrwx 1 jenkins jenkins 14 May 14 2013 latest1.6-64 -> >>>>> jdk1.6.0_45-64 >>>>> lrwxrwxrwx 1 jenkins jenkins 14 Jul 31 2013 latest1.7 -> >>>> jdk1.7.0_25-32 >>>>> lrwxrwxrwx 1 jenkins jenkins 14 Jul 31 2013 latest1.7-32 -> >>>>> jdk1.7.0_25-32 >>>>> lrwxrwxrwx 1 jenkins jenkins 14 Jul 31 2013 latest1.7-64 -> >>>>> jdk1.7.0_25-64 >>>>> >>>>> >>>>> With the actual versions installed: >>>>> >>>>> drwxr-xr-x 9 jenkins jenkins 4096 Jul 23 2011 jdk1.5.0_17-32 >>>>> drwxr-xr-x 9 jenkins jenkins 4096 Jul 23 2011 jdk1.5.0_17-64 >>>>> drwxr-xr-x 9 jenkins jenkins 4096 Jul 23 2011 jdk1.5.0_22-32 >>>>> drwxr-xr-x 9 jenkins jenkins 4096 Jul 23 2011 jdk1.5.0_22-64 >>>>> drwxr-xr-x 10 jenkins jenkins 4096 Jul 23 2011 jdk1.6.0_11-32 >>>>> drwxr-xr-x 10 jenkins jenkins 4096 Jul 23 2011 jdk1.6.0_11-64 >>>>> drwxr-xr-x 10 jenkins jenkins 4096 Jul 23 2011 jdk1.6.0_20-32 >>>>> drwxr-xr-x 10 jenkins jenkins 4096 Jul 23 2011 >>>>> jdk1.6.0_20-32-unlimited-security >>>>> drwxr-xr-x 10 jenkins jenkins 4096 Jul 23 2011 jdk1.6.0_20-64 >>>>> drwxr-xr-x 10 jenkins jenkins 4096 Oct 16 2011 jdk1.6.0_27-32 >>>>> drwxr-xr-x 10 jenkins jenkins 4096 Oct 16 2011 jdk1.6.0_27-64 >>>>> drwxr-xr-x 8 jenkins jenkins 4096 Mar 26 2013 jdk1.6.0_45-32 >>>>> drwxr-xr-x 8 jenkins jenkins 4096 Mar 26 2013 jdk1.6.0_45-64 >>>>> drwxr-xr-x 8 jenkins jenkins 4096 Oct 3 2012 jdk1.7.0_04 >>>>> drwxr-xr-x 8 jenkins jenkins 4096 Jun 6 2013 jdk1.7.0_25-32 >>>>> drwxr-xr-x 8 jenkins jenkins 4096 Jun 6 2013 jdk1.7.0_25-64 >>>>> drwxr-xr-x 10 jenkins jenkins 4096 Jun 27 2011 jdk1.7.0-32 >>>>> drwxr-xr-x 8 jenkins jenkins 4096 Mar 18 2014 jdk1.7.0_55 >>>>> drwxr-xr-x 10 jenkins jenkins 4096 Jun 27 2011 jdk1.7.0-64 >>>>> >>>>> drwxr-xr-x 8 jenkins jenkins 4096 Mar 4 2014 jdk1.8.0 >>>>> >>>>> >>>>> Are these latest/ links explicitly frozen, or simply have been >>>>> neglected for a while? >>>>> >>>> >>>> Neglected I would Imagine. They are different on many machines, and >> also >>>> the >>>> drop-down options in the master gui config don't match. >>>> >>>> As this is not a 5 minute fix, is it possible you can create a BUILDS >>> jira >>>> so someone >>>> can go through this ? >>>> >>>> Thanks >>>> >>>> Gav… >>>> >>>>> >>>>> -steve >>>>> >>>>> -- >>>>> CONFIDENTIALITY NOTICE >>>>> NOTICE: This message is intended for the use of the individual or >>> entity >>>> to >>>>> which it is addressed and may contain information that is >> confidential, >>>>> privileged and exempt from disclosure under applicable law. If the >>> reader >>>>> of this message is not the intended recipient, you are hereby >> notified >>>> that >>>>> any printing, copying, dissemination, distribution, disclosure or >>>>> forwarding of this communication is strictly prohibited. If you have >>>>> received this communication in error, please contact the sender >>>> immediately >>>>> and delete it from your system. Thank You. >>>> >>>> >>> >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity to >> which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender immediately >> and delete it from your system. Thank You. >>
