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

Source build release pipeline should validate the availability of the commit shas #3058

Closed
Tracked by #3460
MichaelSimons opened this issue Oct 11, 2022 · 1 comment
Closed
Tracked by #3460

Source build release pipeline should validate the availability of the commit shas #3058

MichaelSimons opened this issue Oct 11, 2022 · 1 comment
Labels
area-infra Source-build infrastructure and reporting

Comments

@MichaelSimons
Copy link
Member

There are repos that don't have automation around internal to public sha mirroring. This causes a lag when the shas are publicly available. The release pipeline used to create the release announcement should be validating this to avoid situations where an announcement is made but you can create a source-tarball (example)
@dotnet-issue-labeler dotnet-issue-labeler bot added area-build Improvements in source-build's own build process untriaged labels Oct 11, 2022
@MichaelSimons MichaelSimons added area-infra Source-build infrastructure and reporting and removed area-build Improvements in source-build's own build process untriaged labels Oct 13, 2022
@lbussell lbussell mentioned this issue Oct 13, 2022
Closed
@mthalman mthalman mentioned this issue May 18, 2023
Open
15 tasks
@MichaelSimons
Copy link
Member Author

[Triage] This is obsolete with the VMR.

@MichaelSimons MichaelSimons closed this as not planned Won't fix, can't repro, duplicate, stale Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-infra Source-build infrastructure and reporting
Projects
.NET Source Build
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MichaelSimons