Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Jun 19, 2024 7:10:27 AM
Jun 19, 2024 7:10:27 AM
If applying the R2024-05v2 or R2024-06 monthly patch on your CICD instance, and using Jenkins, many or all builds may start to fail without warning. The P2 may be commenting that it was not able to locate some of the component jars in the local .m2 repository; with the folder location mentioned being the "${user.HOME}/.m2/repository", instead of the local repository defined in the settings file. Even if using "-s", "-gs", and/or attempting to force the plugin to use a specific local repository, it will always override the location with ${user.HOME}, and fail to run properly.
This issue may only appear with those environments that use OpenJDK Zulu 17 at this time; instances that use Oracle JDK 17 or other OpenJDK distros do not appear to be affected at this time.
If customers have not upgraded to the R2024-05 monthly patch, we would suggest to continue using the R2024-04 monthly patch and 8.0.15 "builder-maven-plugin". If the upgrade has already happened or in progress, customers should check if they can swap to a different Open JDK instance (such as AdoptOpenJDK), or use Oracle JDK for the time being; until the issue has been fixed.
Currently, Qlik is on track to remediate the issue with a change to the plugins themselves, with a targeted date (at this time) of the July 2024 Monthly Patch.
Due to some changes in the newer versions of Jenkins (both LTS and the nightly versions), the plugins that are used with Jenkins remove some variables that are necessary to be passed to Maven and the P2 itself. Additionally, Zulu JDK has a problem with how the variables are being passed from Jenkins to the Java instance itself.
For additional questions or concerns, please reach out to Talend Support on this issue, and reference this internal defect ID, TUP-43304.