ci: Remove jobs using the aswf-docker 2022 containers#5204
Open
lgritz wants to merge 1 commit into
Open
Conversation
In main (working toward the late-2026/2027 releases) these 2022 containers are both outside the promised 3 year support window, and also are using CentOS 7-based containers that are essentially irrelevant now that all the studios have moved to RHEL9 (and Rocky/Alma) compatible OS distros. So there is really no need to continue CI testing on them for branches aimed at the future. Note that we still have Ubuntu-based "oldest gcc" and "oldest clang" jobs, so dropping this does not actually impact our ability to test against the oldest gcc, C++, and python that we claim to support. Signed-off-by: Larry Gritz <lg@larrygritz.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In main (working toward the late-2026/2027 releases) these 2022 containers are both outside the promised 3 year support window, and also are using CentOS 7-based containers that are essentially irrelevant now that all the studios have moved to RHEL9 (and Rocky/Alma) compatible OS distros. So there is really no need to continue CI testing on them for branches aimed at the future.
Note that we still have Ubuntu-based "oldest gcc" and "oldest clang" jobs, so dropping this does not actually impact our ability to test against the oldest gcc, C++, and python that we claim to support.