Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Musl VMR builds of aspnetcore use wrong RID (linux-X instead of linux-musl-X) #4628

Closed
directhex opened this issue Sep 24, 2024 · 0 comments · Fixed by dotnet/sdk#43667
Closed

Musl VMR builds of aspnetcore use wrong RID (linux-X instead of linux-musl-X) #4628

directhex opened this issue Sep 24, 2024 · 0 comments · Fixed by dotnet/sdk#43667
Labels
area-ci-testing untriaged

Comments

@directhex
Copy link

e.g. on https://dev.azure.com/dnceng/internal/_build/results?buildId=2545542&view=artifacts&pathAsName=false&type=publishedArtifacts we created Microsoft.AspNetCore.App.Runtime.linux-arm64.9.0.0-rc.1.24414.4.nupkg instead of linux-musl-arm64
@directhex directhex mentioned this issue Sep 24, 2024
Merged
directhex added a commit to directhex/sdk that referenced this issue Sep 24, 2024
@directhex
Always override RID in aspnetcore build, not SB-only
89ccf86 
This was mistakenly restricted to source-build-only builds, resulting in incorrect RID being used for Musl VMR builds

Closes: dotnet/source-build#4628
@directhex directhex mentioned this issue Sep 24, 2024
Merged
@github-project-automation github-project-automation bot moved this from Backlog to Done in .NET Source Build Sep 24, 2024
@mmitche mmitche mentioned this issue Sep 25, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-ci-testing untriaged
Projects
.NET Source Build
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Always override RID in aspnetcore build, not SB-only directhex/sdk
1 participant
@directhex