-
Notifications
You must be signed in to change notification settings - Fork 237
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
Deprecate OpenJDK 8 ARM32 and ARM64 at DockerHub in favour of AdoptOpenJDK location #303
Comments
@jerboaa - One other option is to ask OpenJDK upstream to merge in the two aarch64 projects into main |
@karianna There is some plan to merge the Aarch64 port to jdk8u mainline[1], but I don't know anything about 32 bit arm. AFAIK, those trees have diverged in JDK 8-land. [1] http://mail.openjdk.java.net/pipermail/jdk8u-dev/2020-March/011409.html |
A big +1 for this. This is really creating a lot of issues with downstream projects that are using Adopt Images. See this issue for more details. |
@karianna I'm a little bit unsure on what the requirement here is (Replacing dockerhub pushes with an AdoptOpenJDK location?) I wouldn't have thought we'd replace Dockerhub so is this about desyncing the need to ship the two ARM platforms at the same time as the others (which seems like a reasonable requirement) |
Yeah, this is probably the wrong approach. Instead, we should simply automate all of the Docker production on a release and be able to run parts of it as needed. I'll see if I can find the issue tracking docker release automation |
It often takes us an extra week+ to get out the Java 8 aarch64 and 32 builds usually due to late tagging or a TCK failure or intermittent test failures.
This holds up the main DockerHub release.
By moving these two in particular we'll speed up the docker hub releases.
The text was updated successfully, but these errors were encountered: