-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
Decide the future of the Archlinux image: either add "Archlinux JDK17" or remove "Archlinux JDK11" #422
Comments
I prefer to stop updating the archlinux container and announce its end of life. We'll need to do the same end of life announcement for the centos7 containers. This might be a good place to add the arch linux container image to the list of unsupported or upcoming unsupported environments that are noted by the Jenkins core pull request That pull request is not directly applicable to this repository, because this repository is for the agents, while that pull request is for the controller. However, it may be possible to implement an admin monitor that warns about unmaintained or unsupported agent containers. |
Do you have any numbers to share @dduportal ? |
Archlinux will be removed as soon as #890 is delivered. |
Platform SIG meeting discussed further and agreed that merging next week is good. Arch Linux container images will no longer be updated beginning next week. |
What feature do you want to see added?
There is currently an Archlinux JDK11 image introduced in #171.
We've already wondered if we (Jenkins community) should keep maintaining it or remove it:
As discussed in #409 (comment) , let's start by checking numbers: how much pull of the archlinux image do we have and which part of the usage does it represent?
If it is really low, unless some steps up to help maintaining, we should consider deprecating this image.
Ping @fossdd @slide as you were the author/maintainer of the PR introducing Arch Linux: do you feel like maintaining it or deprecating it?
Upstream changes
No response
The text was updated successfully, but these errors were encountered: