Increase Jenkins version to 2.440.3

[mPokornyETM]

Increase Jenkins version 2.440.1 to allow next feature development

Testing done

Submitter checklist

Beta Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

[MarkEWaite]

I was a little surprised by the choice of 2.440.1 as the baseline. The recommendation from the documentation is currently either 2.414.3 or 2.426.3

I'm fine with this change but was surprised. Was there a specific reason you chose this version as the base?

[mPokornyETM]

I was a little surprised by the choice of 2.440.1 as the baseline. The recommendation from the documentation is currently either 2.414.3 or 2.426.3

I'm fine with this change but was surprised. Was there a specific reason you chose this version as the base?

There is no specific reason. The same docu https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/#currently-recommended-versions says, that it might ber used. And we have currently the same version on our productive system. And I dont want to change the version in plugin so rapidly. Therefore the highest as possible.

[MarkEWaite]

@mPokornyETM I've incremented the minimum Jenkins version to 2.440.3 and switched the pom file to use the jenkins.baseline technique that is now used in the Jenkins plugin archetype. That aligns the plugin BOM version number with the minimum Jenkins version.

[mPokornyETM]

Jenkins plugin archetype

Migh you passte here some link with the example please?. Thx

[MarkEWaite]

Might you paste here some link with the example please?. Thx

The Jenkins plugin archetype has been updated to include a baseline version string (jenkins.baseline) that is used to provide both the Jenkins minimum version (jenkins.version) and the artifactId of the plugin BOM. Refer to the pull request:

• Add jenkins.baseline variable to reduce manual bom update mistakes archetypes#737

A request has also been made that recommends an OpenRewrite recipe be created to perform the transformation so that it can be done more easily. That request is:

• Incomplete migration: jenkins.baseline archetypes#738

This pull request is manually performing the transformation that eventually it is hoped will be done with an OpenRewrite recipe. There are already many useful OpenRewrite recipes for Jenkins in addition to the more general OpenRewrite recipes for Java development that can be used for Jenkins plugins.