Bump Jenkins LTS versions to 2.414.2 in various parts of the documentation

[github-actions]

Bump last three Jenkins' LTS versions in the documentation

Bump Jenkins minimum BOM artifact version in the "plugin-bill-of-materials" page

1 file(s) updated with "${1}2465.va_e76ed7b_3061${3}": * content/doc/developer/tutorial-improve/use-plugin-bill-of-materials.adoc

Bump Jenkins minimum BOM artifact in the "plugin-bill-of-materials" page

1 file(s) updated with "${1}bom-2.387.x${3}": * content/doc/developer/tutorial-improve/use-plugin-bill-of-materials.adoc

Bump Jenkins minimum BOM artifact in the "dependency management" page

1 file(s) updated with "${1}bom-2.387.x${3}": * content/doc/developer/plugin-development/dependency-management.adoc

Bump Jenkins minimum BOM artifact version in the "dependency management" page

1 file(s) updated with "${1}2465.va_e76ed7b_3061${3}": * content/doc/developer/plugin-development/dependency-management.adoc

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[MarkEWaite]

This is a very nice improvement. Thanks very much!

I was a little surprised that the destination bom version is not the most recent release, but the release before that. Merging because this is a great step in the right direction. It would be a nice future addition if it offered the most recent release.

[gounthar]

You're right, Mark, we should have had:

<dependency>
    <groupId>io.jenkins.tools.bom</groupId>
    <artifactId>bom-2.387.x</artifactId>
    <version>2373.v18527128f2a_c</version>
    <type>pom</type>
</dependency>

That's a mystery I'll have to solve. 🤔

[gounthar]

@MarkEWaite : in https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/bom-2.387.x/maven-metadata.xml I see:

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>io.jenkins.tools.bom</groupId>
  <artifactId>bom-2.387.x</artifactId>
  <versioning>
    <latest>2465.va_e76ed7b_3061</latest>
    <release>2483.v3b_22f030990a_</release>
    <versions>
[...]

No wonder updatecli chose 2465.va_e76ed7b_3061 over 2483.v3b_22f030990a_.
Is it a normal behavior, or do we have an issue?
Thanks.

[MarkEWaite]

@MarkEWaite : in https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/bom-2.387.x/maven-metadata.xml I see:

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>io.jenkins.tools.bom</groupId>
  <artifactId>bom-2.387.x</artifactId>
  <versioning>
    <latest>2465.va_e76ed7b_3061</latest>
    <release>2483.v3b_22f030990a_</release>
    <versions>
[...]

No wonder updatecli chose 2465.va_e76ed7b_3061 over 2483.v3b_22f030990a_. Is it a normal behavior, or do we have an issue? Thanks.

That's a fascinating inconsistency. I don't have an explanation for it. Here is some data to show the inconsistency:

• bom-2.387.x has latest == 2465.x and release == 2483.x
• bom-2.401.x has latest == 2465.x and release == 2483.x
• bom-2.414.x has latest == 2483.x and release == 2483.x

In all cases, the release attribute is correct. If updatecli can be taught to use the release attribute, that is a better choice than the latest attribute.