Skip to content

[9.0.1xx-preview5] Alpine Artifact Changed from 3.19 to 3.19.1 #4446

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

Closed
Winniexu01 opened this issue Jun 4, 2024 · 1 comment
Closed

[9.0.1xx-preview5] Alpine Artifact Changed from 3.19 to 3.19.1 #4446

Winniexu01 opened this issue Jun 4, 2024 · 1 comment
Labels
ops-monitor Issues created/handled by the source build monitor role

Comments

@Winniexu01
Copy link
Member

Related to #4393

This issue has been fixed on main build but now fails on the release/9.0.1xx-preview5 branch: https://dev.azure.com/dnceng/internal/_build/results?buildId=2466083&view=logs&j=4d1a2973-f2d0-574a-8c51-e8b42bd01a3f&t=c8784a9d-200f-5224-43b9-a4a830b95fb2

artifacts (internal Microsoft SDK), the alpine target RID was 3.19-x64 but is now 3.19.1-x64, so the pipeline build failed to find the SDK tarball.

@Winniexu01 Winniexu01 added ops-monitor Issues created/handled by the source build monitor role and removed untriaged area-ci-testing labels Jun 4, 2024
@Winniexu01
Copy link
Member Author

new Alpine run (internal Microsoft link) is green. Close this issue.

@github-project-automation github-project-automation bot moved this from Backlog to Done in .NET Source Build Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ops-monitor Issues created/handled by the source build monitor role
Projects
Archived in project
Development

No branches or pull requests

1 participant