feat(java): Require Jenkins core 2.479.3 and Java 17.#82
Closed
gounthar wants to merge 4 commits intojenkinsci:masterfrom
Closed
feat(java): Require Jenkins core 2.479.3 and Java 17.#82gounthar wants to merge 4 commits intojenkinsci:masterfrom
gounthar wants to merge 4 commits intojenkinsci:masterfrom
Conversation
Contributor
Author
|
Hi @MarkEWaite, Would you mind replaying this build with the supplied Jenkinsfile? These modifications build successfully on my machine. Thanks. |
bluesliverx
pushed a commit
to bluesliverx/github-pr-comment-build-plugin
that referenced
this pull request
Mar 6, 2025
MarkEWaite
suggested changes
Mar 6, 2025
Comment on lines
+69
to
+79
| <dependencyManagement> | ||
| <dependencies> | ||
| <dependency> | ||
| <groupId>io.jenkins.tools.bom</groupId> | ||
| <artifactId>bom-${jenkins.baseline}.x</artifactId> | ||
| <version>4228.v0a_71308d905b_</version> | ||
| <scope>import</scope> | ||
| <type>pom</type> | ||
| </dependency> | ||
| </dependencies> | ||
| </dependencyManagement> |
There was a problem hiding this comment.
Replay failed due to this duplication of dependencyManagement section
Suggested change
| <dependencyManagement> | |
| <dependencies> | |
| <dependency> | |
| <groupId>io.jenkins.tools.bom</groupId> | |
| <artifactId>bom-${jenkins.baseline}.x</artifactId> | |
| <version>4228.v0a_71308d905b_</version> | |
| <scope>import</scope> | |
| <type>pom</type> | |
| </dependency> | |
| </dependencies> | |
| </dependencyManagement> |
bluesliverx
added a commit
that referenced
this pull request
Mar 6, 2025
chore(dependencies) Make changes from #82
Contributor
|
Closed in favor of #84 |
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
3 participants
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
github-pr-comment-builddevelopers! 👋This is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:
Upgrade to the next major parent version (5.X) requiring Jenkins 2.479 and Java 17
io.jenkins.tools.pluginmodernizer.UpgradeNextMajorParentVersion
Why Upgrade to Java 17 and Jenkins 2.479.x?
Embrace Java 17 LTS Stability: Benefit from long-term support with modern language features that improve development practice and plugin performance.
Harness Jenkins 2.479.x Innovations: Stay aligned with the latest features and stability improvements, ensuring smooth integration and future-proofing.
Enhance Security: Protect your plugin with up-to-date security fixes from both Java 17 and Jenkins core improvements.
Align with the Community: Keep pace with ecosystem shifts towards Java 17, ensuring compatibility and expanding your plugin's user base.
Enjoy a Better Developer Experience: Make the most of advanced tooling support and simplified dependency management with Java 17's enhancements.
Summary
By upgrading, you'll be positioning your plugin at the forefront of performance, security, and user satisfaction. We encourage you to explore these updates and provide feedback. Let's continue to build a robust Jenkins ecosystem together!