Hi all, I updated the jenkins-slave and dist-test-slave images, in order for the jenkins slaves to pick up the new Java version, I'll have to restart the running instances. There might be some jenkins job failures in the coming hours, if unsuccessful will revert the previous images.
Best, Zoltan On Thu, Feb 26, 2026 at 5:56 PM Zoltan Chovan <[email protected]> wrote: > Hi all, > > Unfortunately, I couldn't execute the migration today. It turned out that > the jenkins-slaves also need some modifications, and they run differently > than the dist-test-slave instances. I have a plan to execute tomorrow, but > testing it is proving more difficult than expected. Nevertheless, the plan > is to have this finished tomorrow. > > Thanks for your patience and understanding, > > Zoltan > > On Tue, Feb 24, 2026 at 12:12 PM Zoltan Chovan <[email protected]> wrote: > >> Hi all, >> >> In order to be able to fully switch to JDK17, we need to update our >> infrastructure. Currently dist-test slaves only have JDK 7 and 8 installed, >> with no way of switching between them. I have prepared and test new docker >> images so that switching between JDKs is possible (via using jenv local >> <version>) so that we can still test maintenance releases with JDK8, after >> the switch is done. Additionally we'll need to update the build-and-test.sh >> script so that it can set the correct JDK version to use. >> >> My plan is to make the change this Thursday (Feb 26), after that if the >> correct label is included in the commit message (e.g. USE_JAVA_17), >> otherwise JDK8 will be used. >> After https://gerrit.cloudera.org/c/23259/ is merged, we can switch to >> JDK17 being the default. >> >> Please let me know if you have any questions, or if you need me to delay >> this work for some reason (e.g. important changes need to be merged, etc) >> >> Best regards, >> Zolta >> >
