wcf icon indicating copy to clipboard operation
wcf copied to clipboard
verified publisher icon dotnet

Migrate off of EOL container images

Open mthalman opened this issue 1 year ago • 5 comments

The following container images are unsupported to the distro being EOL and should be updated to supported versions:

https://github.com/dotnet/wcf/blob/ed1bd7a975c290a65ff3db56c775445d84f44f3f/eng/SendToHelix.proj#L34 https://github.com/dotnet/wcf/blob/ed1bd7a975c290a65ff3db56c775445d84f44f3f/eng/SendToHelix.proj#L40 https://github.com/dotnet/wcf/blob/ed1bd7a975c290a65ff3db56c775445d84f44f3f/eng/SendToHelix.proj#L42 https://github.com/dotnet/wcf/blob/ed1bd7a975c290a65ff3db56c775445d84f44f3f/eng/SendToHelix.proj#L44

Related: Debian 11: https://github.com/dotnet/core/issues/9625 Fedora 38: https://github.com/dotnet/core/issues/9291

mthalman avatar Nov 26 '24 22:11 mthalman

@mthalman, can you provide us with a versionless docker container names/tags that just represents the latest of the distro so that we don't need to maintain these?

mconnew avatar Dec 03 '24 19:12 mconnew

@mthalman, can you provide us with a versionless docker container names/tags that just represents the latest of the distro so that we don't need to maintain these?

There are no such tags and we explicitly do not want them to avoid the potential for breaking the build. Coincidentally, this is specifically called out at https://github.com/dotnet/dotnet-buildtools-prereqs-docker/pull/1274/files#diff-59c2cf35a49a17d78cfac4d681eca2c123f5c0ea49579b99b284916b1628f395R52.

mthalman avatar Dec 03 '24 20:12 mthalman

Our build has never been broken due to moving distro versions. We have had multiple build breakages due to expiring OS versions (it was Helix queues for specific distribution versions were retired without notification, but it'sthe same underlying issue, the need to keep updating the send to helix config). For this repo at least, we would have better build stability if there was a latest tag than we've had with the distro product version being locked down.

mconnew avatar Dec 04 '24 05:12 mconnew

I would suggest logging an issue at https://github.com/dotnet/dotnet-buildtools-prereqs-docker/issues to make your case on why this would be useful.

mthalman avatar Dec 04 '24 15:12 mthalman

For reference purposes, here's the follow-up issue that was created: https://github.com/dotnet/dotnet-buildtools-prereqs-docker/issues/1279

mthalman avatar Dec 18 '24 16:12 mthalman