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

Stop testing Java 11 #1282

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

MarkEWaite
Copy link
Contributor

Stop testing Java 11

Jenkins stopped supporting Java 11 with the release of Jenkins 2.463 (weekly) and Jenkins 2.479.1 (LTS). Most plugins stopped spending ci.jenkins.io time to run tests that are specific to Java 11.

Let's save money and time by removing the Java 11 test configuration. It has not found any issues that are not also found with Java 17 and Java 21.

Jenkins plugin BOM still tests with Java 11 on older lines (currently 2.452.x and 2.462.x) and the plugin build will continue to generate Java 11 byte code until the parent pom is upgraded to 5.x and the minimum Jenkins version is upgraded to 2.479.1.

We don't expect to release a new version of this plugin, since the AWS SDK for Java v1 was deprecated 31 July 2024 and will only receive security fixes until its end of life 31 Dec 2025. However, there is not much justification to continue testing Java 11 on the plugin when it is already well tested by plugin BOM and Java 11 is no longer supported by Jenkins.

Testing done

None. Rely on testing by ci.jenkins.io

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

Jenkins stopped supporting Java 11 with the release of Jenkins 2.463
(weekly) and Jenkins 2.479.1 (LTS).  Most plugins stopped spending
ci.jenkins.io time to run tests that are specific to Java 11.

Let's save money and time by removing the Java 11 test configuration.
It has not found any issues that are not also found with Java 17 and
Java 21.

Jenkins plugin BOM still tests with Java 11 on older lines (currently
2.452.x and 2.462.x) and the plugin build will continue to generate Java
11 byte code until the parent pom is upgraded to 5.x and the minimum
Jenkins version is upgraded to 2.479.1.

We don't expect to release a new version of this plugin, since the AWS SDK
for Java v1 was deprecated 31 July 2024 and will only receive security
fixes until its end of life 31 Dec 2025.  However, there is not much
justification to continue testing Java 11 on the plugin when it is already
well tested by plugin BOM and Java 11 is no longer supported by Jenkins.
@MarkEWaite MarkEWaite requested a review from a team as a code owner January 10, 2025 00:59
@Vlatombe Vlatombe enabled auto-merge (squash) January 10, 2025 08:24
@Vlatombe Vlatombe closed this Jan 10, 2025
auto-merge was automatically disabled January 10, 2025 08:24

Pull request was closed

@Vlatombe Vlatombe reopened this Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants