-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch default baseline for new plugins to 2.361.x #546
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that make a lot of sense!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should perhaps wait until 2.375.1 is released
+1 for this proposal and +1 for this PR.
Ack, will remind myself to check up later this week. |
Development list thread: https://groups.google.com/g/jenkinsci-dev/c/pjfvsMw-EMM/m/OIw_hveUBwAJ |
jenkinsci/archetypes#546 has switched the default baseline for new plugins to 2.361.4. https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/ recommends either 2.346.3 or 2.361.4 as the core dependency. Jenkins plugin development tools are switching to require Java 11 as well.
Closes #542. Also see jenkins-infra/jenkins.io#5731. As per https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/ we should perhaps wait until 2.375.1 is released, though that should happen by the time this PR actually goes live anyway.