Skip to content
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

Remove 2.375.x support #2218

Merged
merged 2 commits into from
Jun 27, 2023
Merged

Remove 2.375.x support #2218

merged 2 commits into from
Jun 27, 2023

Conversation

MarkEWaite
Copy link
Contributor

@MarkEWaite MarkEWaite commented Jun 26, 2023

Remove 2.375.x support

Many of the plugin versions managed by the plugin bill of materials have been updated to require Jenkins 2.387.1 or newer. Those plugins include:

Over 15% of the plugins in the bill of materials already require a core version newer than 2.375.4.

There are relatively few plugins that require Jenkins 2.375.x.

The benefits of testing for compatibility with Jenkins 2.375.x decrease each time a plugin requires a version newer than 2.375.x.

The last two releases of the plugin bill of materials included no plugin version changes in the bom-2.375.x set. One plugin version was pinned to 2.375.x, and multiple maven plugins were updated, but no plugin versions were updated.

Rather than continuing to add more pinned plugins for Jenkins 2.375.x compatibility, let's stop 2.375.x plugin bill of materials updates and limit updates to 2.387.x, 2.401.x, and weekly.

Users of previous bill of materials releases can continue to use them, but new releases will only cover 2.387.x and 2.401.x. changes

Testing done

  • mvn clean --pl sample-plugin -P 2.387.x verify
  • mvn clean --pl sample-plugin -P 2.401.x verify
  • mvn clean --pl sample-plugin verify

Submitter checklist

Many of the plugin versions managed by the plugin bill of materials have
been updated to require Jenkins 2.387.1 or newer.  Those plugins include:

* https://plugins.jenkins.io/bootstrap5-api/ - Bootstrap 5 API
* https://plugins.jenkins.io/branch-api/ - Branch API
* https://plugins.jenkins.io/checks-api - GitHub checks API
* https://plugins.jenkins.io/configuration-as-code - Configuration as code
* https://plugins.jenkins.io/credentials/ - Credentials
* https://plugins.jenkins.io/custom-folder-icon - Configuration as code
* https://plugins.jenkins.io/data-tables-api/ - Data tables API
* https://plugins.jenkins.io/echarts-api/ - echarts API
* https://plugins.jenkins.io/font-awesome-api/ - Font awesome API
* https://plugins.jenkins.io/forensics-api/ - Forensics API
* https://plugins.jenkins.io/git-client/ - Git client
* https://plugins.jenkins.io/git/ - Git
* https://plugins.jenkins.io/junit/ - JUnit
* https://plugins.jenkins.io/junit-attachments/ - JUnit attachments
* https://plugins.jenkins.io/lockable-resources/ - Lockable resources
* https://plugins.jenkins.io/pipeline-build-step/ - Pipeline: build step
* https://plugins.jenkins.io/pipeline-model-definition/  - Pipeline: declarative
* https://plugins.jenkins.io/plugin-util-api - Plugin utilities API
* https://plugins.jenkins.io/workflow-cps/ - Pipeline: Groovy
* https://plugins.jenkins.io/workflow-multibranch/ - Pipeline: Multibranch
* https://plugins.jenkins.io/workflow-scm-step/ - Pipeline: SCM step

Over 10% of the plugins in the bill of materials require a core version
newer than 2.375.4.

There are relatively few plugins that require Jenkins 2.375.x.

The benefits of testing for compatibility with Jenkins 2.375.x decrease
each time a plugin requires a version newer than 2.375.x.

The last two releases of the plugin bill of materials included no plugin
version changes in the bom-2.375.x set.  One plugin version was pinned to
2.375.x, and multiple maven plugins were updated, but no plugin versions
were updated.

Rather than continuing to add more pinned plugins for Jenkins 2.375.x
compatibility, let's stop 2.375.x plugin bill of materials updates and
limit updates to 2.387.x, 2.401.x, and weekly.

Users of previous bill of materials releases can continue to use them,
but new releases will only cover 2.387.x and 2.401.x.
change
@MarkEWaite MarkEWaite requested a review from a team as a code owner June 26, 2023 22:20
@jglick jglick added the full-test Test all LTS lines in this PR and do not halt upon first error. label Jun 26, 2023
@jglick jglick enabled auto-merge (squash) June 26, 2023 23:27
@jglick jglick merged commit 700c506 into jenkinsci:master Jun 27, 2023
@MarkEWaite MarkEWaite deleted the drop-bom-2.375.x branch June 27, 2023 03:14
@jglick
Copy link
Member

jglick commented Jun 27, 2023

@MarkEWaite are you planning to release this? https://github.com/jenkinsci/bom/runs/14576031250

@MarkEWaite
Copy link
Contributor Author

@MarkEWaite are you planning to release this? https://github.com/jenkinsci/bom/runs/14576031250

I was planning to release it at the end of the week. I'd like to include two additional changes in the next release of the plugin BOM:

Does it need to be released sooner than the end of the week?

@jglick
Copy link
Member

jglick commented Jun 27, 2023

Of course not, just checking that you had not forgotten that release on matching labels is no longer automatic.

@jglick
Copy link
Member

jglick commented Jun 28, 2023

sghill added a commit to openrewrite/rewrite-jenkins that referenced this pull request Aug 16, 2023
bom-2.375.x is no longer being published.
jenkinsci/bom#2218
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking full-test Test all LTS lines in this PR and do not halt upon first error.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants