Our take on that one was to simply manually package the IBM JDK into some .zip file and push it into our nexus instance, then configure the URL manually in the Jenkins autoinstall UI. Then Jenkins will use it just the same way it does with Oracle JDK. It gives an additional work, sure, but it's a one time manipulation that does not happen that often.
HTH. Cheers 2014-09-22 12:11 GMT+02:00 Jochen Hinrichsen <[email protected] >: > Dear group, > > i'm running a couple of jenkins slaves, happily using the JDK auto > installer except for the one poor AIX/ ppc64 slave. After checking > JDKInstaller.java, it seems to me that it only supports JDKs from Oracle. > AIX JDKs are released by IBM. What would be the easiest way, even > considering one time manual workarounds, for this problem? > > Currently, the destination directory tools/model.HUDSON.JDK is deleted > (line 121) before the 'Unknown CPU name: aix' is thrown in line 124. This > is bad because i cannot drop a JDK manually. I'd prefer Jenkins to leave > the filesystem unchanged if it detects unsupported combinations of OS and > CPU. > > I also fiddled around with .installedByHudson, but it seems that i cannot > produce the correct ID expected in line 118 to fool Jenkins into thinking > the JDK is already installed. > > Any ideas? > > Thanks in advance > > Jochen > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! nbsp;! -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
