We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In dotnet/runtime we bumped most docker images to azurelinux-3.0 ones: https://github.com/dotnet/runtime/blob/2a80808f86459a95229c6f9c85ce32b62636fceb/eng/pipelines/common/templates/pipeline-with-resources.yml#L20
However the VMR unified build still uses the cbl-mariner-2.0 ones: https://github.com/dotnet/sdk/blob/5a8b156bcc5b496d6de43c8cece1bacbb7fee46f/eng/pipelines/templates/variables/vmr-build.yml#L25-L42
We should make sure to keep these images aligned.
/cc @jkoritzinsky @ViktorHofer
The text was updated successfully, but these errors were encountered:
Sounds reasonable. Do we just need to update the docker images in vmr-build.yml or is there more to it?
Sorry, something went wrong.
That should be it. We just need to remember to consistently do this until the VMR goes live and we remove the runtime official build.
Successfully merging a pull request may close this issue.
In dotnet/runtime we bumped most docker images to azurelinux-3.0 ones:
https://github.com/dotnet/runtime/blob/2a80808f86459a95229c6f9c85ce32b62636fceb/eng/pipelines/common/templates/pipeline-with-resources.yml#L20
However the VMR unified build still uses the cbl-mariner-2.0 ones:
https://github.com/dotnet/sdk/blob/5a8b156bcc5b496d6de43c8cece1bacbb7fee46f/eng/pipelines/templates/variables/vmr-build.yml#L25-L42
We should make sure to keep these images aligned.
/cc @jkoritzinsky @ViktorHofer
The text was updated successfully, but these errors were encountered: