Skip to content

feat(java): Require Jenkins core 2.479.3 and Java 17.#25

Open
gounthar wants to merge 12 commits intojenkinsci:masterfrom
gounthar:plugin-modernizer/upgradenextmajorparentversion
Open

feat(java): Require Jenkins core 2.479.3 and Java 17.#25
gounthar wants to merge 12 commits intojenkinsci:masterfrom
gounthar:plugin-modernizer/upgradenextmajorparentversion

Conversation

@gounthar
Copy link
Contributor

@gounthar gounthar commented Jan 13, 2025

Hello date-parameter developers! 👋

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

Upgrade to the next major parent version (5.X) requiring Jenkins 2.479 and Java 17.

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.

Removing developers Tag from pom.xml

Jenkins no longer requires the developers tag in pom.xml, as the developers section was traditionally used to list individuals responsible for the plugin.
Instead, Jenkins now uses the Repository Permission Updater (RPU) to manage permissions and developer information.

Benefits of Removing developers Tag:
  • Simplification: Removes unnecessary metadata from the pom.xml, resulting in a cleaner and more maintainable file.
  • Consistency: Centralizes developer information management through the RPU, minimizing discrepancies.
  • Security: Utilizes the RPU's controlled permission management, enhancing the security of artifact deployments.

Removing the developers tag aligns with modern Jenkins infrastructure standards and prevents outdated or redundant developer information from being included in plugin metadata.

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!

@gounthar gounthar force-pushed the plugin-modernizer/upgradenextmajorparentversion branch from 695600c to 5db9080 Compare January 13, 2025 13:59
}

public FormValidation doCheckDefaultValue(@QueryParameter String dateFormat, @QueryParameter String defaultValue) {
public FormValidation doCheckDefaultValue(

Check warning

Code scanning / Jenkins Security Scan

Stapler: Missing permission check Warning

Potential missing permission check in DescriptorImpl#doCheckDefaultValue
}

public FormValidation doCheckDefaultValue(@QueryParameter String dateFormat, @QueryParameter String defaultValue) {
public FormValidation doCheckDefaultValue(

Check warning

Code scanning / Jenkins Security Scan

Stapler: Missing POST/RequirePOST annotation Warning

Potential CSRF vulnerability: If DescriptorImpl#doCheckDefaultValue connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST
@gounthar gounthar force-pushed the plugin-modernizer/upgradenextmajorparentversion branch from 1d7fd9f to 5303e97 Compare February 27, 2025 07:41
@gounthar gounthar changed the title Require 2.479.1 and Java 17 feat(java): Require Jenkins core 2.479.1 and Java 17. Feb 27, 2025
@gounthar gounthar changed the title feat(java): Require Jenkins core 2.479.1 and Java 17. feat(java): Require Jenkins core 2.479.3 and Java 17. Feb 27, 2025
@gounthar gounthar force-pushed the plugin-modernizer/upgradenextmajorparentversion branch from 5303e97 to 96abfc6 Compare February 27, 2025 07:53
@gounthar
Copy link
Contributor Author

Hi @MarkEWaite,

Would you mind replaying this build with the supplied Jenkinsfile? These modifications build successfully on my machine.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant