Add 2.462.x release line, remove 2.426.x

[MarkEWaite]

Add 2.462.x line, remove 2.426.x line

• Add 2.462.x release line
• Remove 2.426.x line
• Replace 2.426 with 2.440 in documentation
• Use 2.452.3 instead of 2.452.1 as 2.452.x Jenkins version
• Document the final 2.426.x BOM version

Fixes #3301

Testing done

Confirmed that mvn clean verify and PLUGINS=structs,mailer TEST=InjectedTest bash local-test.sh pass locally.

Submitter checklist

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

[jglick]

Did you forget to update

bom/bom-2.452.x/pom.xml

Line 20 in 2dd9d95

<artifactId>bom-weekly</artifactId>

?

[MarkEWaite]

Did you forget to update

bom/bom-2.452.x/pom.xml

Line 20 in 2dd9d95

<artifactId>bom-weekly</artifactId>

?

Thanks very much for catching that mistake! Corrected as 99a27d3

[jglick]

Passing now @MarkEWaite; did you plan to merge & release?

[MarkEWaite]

Passing now @MarkEWaite; did you plan to merge & release?

Thanks for asking. I thought that we'd run the weekly release tomorrow without this change and then merge it and release it at the end of next week. The first release candidate of 2.462.1 will be available Wednesday then the first BOM release with the 2.462.x profile will be available on Friday or Saturday.

Let me know if there is a specific benefit to merging sooner. I'm happy to merge sooner, but didn't want to drop the 2.426.x line until after the 2.462.1 RC was available.

[MarkEWaite]

I'm intentionally leaving the conflict in this pull request until the next time that I want to perform a full test of the latest changes on the master branch.

[MarkEWaite]

I'm intentionally leaving the conflict in this pull request until the next time that I want to perform a full test of the latest changes on the master branch.

I've resolved the conflict to test the merge of the ssh-credentials 342.x release that arrived in:

• Bump org.jenkins-ci.plugins:ssh-credentials from 337.v395d2403ccd4 to 342.ve5a_f1db_5a_132 in /bom-weekly #3402

Full test has started and should confirm that change is passing tests. Before submitting the most recent change, I confirmed passing results for:

$ mvn clean verify
$ PLUGINS=ssh-credentials TEST=InjectedTest bash local-test.sh

Once full tests pass, I plan to merge this.

Tests failed due to a test dependency issue exposed by ssh-credentials update to most recent parent pom and the inclusion of an updated trilead API optional dependency. After reverting ssh-credentials, was able to try again.