feat(ci): Builds on the Jenkins Infrastructure #19
Conversation
This file contains 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
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Hello
compuware-zadviser-apidevelopers! 👋This is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:
Setup the Jenkinsfile
io.jenkins.tools.pluginmodernizer.SetupJenkinsfile
Why is this important?
Starting with the Jenkins 2.463 weekly release, Jenkins now requires Java 17 or newer.
The first Long-Term Support (LTS) release requiring Java 17 or newer (version 2.479.x) was released at the end of October 2024.
The Jenkins core team strongly recommends that all users adopt either Java 17 or Java 21.
The adoption of Java 17 has almost surpassed that of Java 11, and the usage of Java 21 is rapidly increasing.
There will come a time when we no longer support plugins built with JDK 8 or 11.
While this PR does not automatically make your plugin compatible with Java 17 or 21, it represents the first step towards a new era. Your plugin will be built and tested within the Jenkins infrastructure using Java 17 and 21.
After this PR is merged, we will submit additional automated PRs to enable your plugin to build with Java 17 and 21.