Determine naming conventions for non-dockerhub container pushes
This is a list of naming conventions we have in the different repositories which we use which can be used as input to what we do in the future, particularly for an alternate repository for the end-user temurin images.
While we will likely leave the dockerhub ones as-is, since we are now aiming to push to alternate repositories we should look at the naming conventions in use and select which ones to use for the test-container publishing (Will likely be moved to adoptium_test_image instead of test-containers on ghcr to avoid confusion and align with the build image naming).
The expectation is that all of the images pushed to locations other than dockerhub will be verifiable using sigstore.
Naming conventions already in use:
- dockerhub official images:
eclipse-temurin:8u472-b08-jdk-ubi9-minimal,8-jdk-ubi9-minimal,8-jdk,8
- adoptopenjdk official images
- Similar to the above - no longer maintained e.g.
adoptopenjdk/8u292-b10-jre-openj9-0.26.0
- Similar to the above - no longer maintained e.g.
- adoptopenjdk standard (updated by openjdk_build_docker_multiarch)
- Separate per version e.g.
adoptopenjdk/openjdk8:aarch64-ubi-jdk8u292-b10-slimorjdk8u292-b10-ubi-slimorubi-slim
- Separate per version e.g.
- build images (under same adoptopenjdk repo as the last one - updated by centos7_docker_image_updater)
adoptopenjdk/centos7_build_image:linux-amd64or justadoptopenjdk/centos7_build_image
- GHCR test-containers (Updated by test_image_updater
ghcr.io/adoptium/test-containers:ubi10-arm64orghcr.io/adoptium/test-containers:ubi10
- GHCR build images - updated by build_image_updater)
ghcr.io/adoptium/adoptium_build_image:centos7_linux-arm64orcentos7