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

Don't do CI builds for obsolete JDKs #1185

Merged
merged 1 commit into from Jan 3, 2023

Conversation

swankjesse
Copy link
Member

This is motivated by an accute problem with OpenJDK 10, which is consistently failing in CI for reasons wholy unrelated to Okio.

> Configure project :android-test
Unable to detect AGP versions for included builds. All projects in the build should use the same AGP version. Class name for the included build object: org.gradle.composite.internal.DefaultIncludedBuild$IncludedBuildImpl_Decorated.
e: /home/runner/work/okio/okio/android-test/build.gradle.kts:18:1: Unresolved reference: android

It's likely Gradle or AGP or something doesn't work on Java 10, even though it does work on Java 8, Java 9, Java 11, and Java 12.

I'm not interested in debugging this problem; the right fix for it is 'Upgrade to a newer JDK'.

I've specifically dropped unmaintained JDKs according to this page: https://en.wikipedia.org/wiki/Java_version_history

This is motivated by an accute problem with OpenJDK 10, which
is consistently failing in CI for reasons wholy unrelated to
Okio.

    > Configure project :android-test
    Unable to detect AGP versions for included builds. All projects in the build should use the same AGP version. Class name for the included build object: org.gradle.composite.internal.DefaultIncludedBuild$IncludedBuildImpl_Decorated.
    e: /home/runner/work/okio/okio/android-test/build.gradle.kts:18:1: Unresolved reference: android

It's likely Gradle or AGP or something doesn't work on Java 10,
even though it does work on Java 8, Java 9, Java 11, and Java 12.

I'm not interested in debugging this problem; the right fix for
it is 'Upgrade to a newer JDK'.

I've specifically dropped unmaintained JDKs according to this page:
https://en.wikipedia.org/wiki/Java_version_history
@JakeWharton
Copy link
Member

From the perspective of OpenJDK, all builds other than 19 are obsolete. There is no intrinsic concept of LTS in the OpenJDK. Vendors can make any version an LTS if they want to.

There should really only be a single build JDK, the latest, but multiple test JDKs.

@swankjesse swankjesse merged commit 8e559fd into master Jan 3, 2023
@swankjesse swankjesse deleted the jwilson.0102.test_fewer_jdks branch January 3, 2023 14:55
@swankjesse
Copy link
Member Author

I’ve come to think of it like 1.x, 2.x, 3.x, where only major versions get security patches. But instead of 1.x, 2.x, and 3.x, the major versions are inexplicably 8.x, 11.x, and 17.x.

@JakeWharton
Copy link
Member

Vendors like Azul support 13.x and 15.x still. Any vendor can backport security patches to any version if they choose to.

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.

None yet

2 participants