Update alpine-3.17 to alpine-3.19-WithNode#18209
Conversation
MichaelSimons
left a comment
There was a problem hiding this comment.
What impact is this going to have on the PreviousSourceBuildSdk artifact? Is it now going to start looking for an alpine3.19 artifact in the source-build-artifacts blob storage and fail because right now there is only a alpine3.17 artifact?
Yes. The alpine Stage 2 leg will fail until we upload the artifacts from a successful alpine 3.19 Stage 1 build into blob storage. I would have ideally preferred this new container image to be alpine3.17 to avoid this, since this change to 3.19 will ultimately delay a clean build of the VMR. |
|
So essentially what this means is that we'll need to re-bootstrap after we get a build from these changes. |
|
Build fails (as expected) because the alpine-3.19 sdk does not exist. |
Fixes dotnet/source-build#3920
Note that the alpine-3.19 artifacts will need to be uploaded due to changing the artifacts rid from
alpine.3.17-x64toalpine-3.19-x64.