Update Jenkinsfile to use JDK 21 for JBang tests#22691
Open
apupier wants to merge 1 commit intoapache:mainfrom
Open
Update Jenkinsfile to use JDK 21 for JBang tests#22691apupier wants to merge 1 commit intoapache:mainfrom
apupier wants to merge 1 commit intoapache:mainfrom
Conversation
Signed-off-by: Aurélien Pupier <apupier@ibm.com>
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
Contributor
Author
|
I modified the script on Jenkins on this build https://ci-builds.apache.org/job/Camel/job/Camel%20Jbang%20IT%20Tests/job/main/435/cloudbees-pipeline-explorer/ we can notice that it goes further (even if failing) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
given that there is now an enforcer to compile with JDK 21 by default. I propose this first iteration to jhave green build back.
ideally, we should compile with JDK 21 and tests with JDK 17, 21 and 25.
A good intermediate step which shoudl be enough would be to create a matrix jobs whcih is compiling and testing with JDK 17, 21 and 25 with the JDk 17 one skipping the enforcer java rule.
Note that I also removed the branches from the triggeres as there are specific jobs for that
Target
mainbranch)Tracking
Apache Camel coding standards and style
mvn clean install -DskipTestslocally from root folder and I have committed all auto-generated changes.