Skip to content

Validate VMR Shipping Packages #45836

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

Merged
merged 4 commits into from
Jan 27, 2025

Conversation

ellahathaway
Copy link
Member

@ellahathaway ellahathaway commented Jan 9, 2025

Closes dotnet/source-build#4068

When not all packages are signed, the validation stage is marked with a warning and an error message is outputted to the UI.

image

Note: Until dotnet/source-build#4678 is resolved, the validation stage will output the error that not all packages are signed. This is because mac & linux builds are currently doing dry-run signing.

@ellahathaway ellahathaway force-pushed the validate-signed-artifacts branch from 2ff6121 to c818ebe Compare January 23, 2025 18:18
@ellahathaway
Copy link
Member Author

ellahathaway commented Jan 23, 2025

Test run (internal Microsoft link)

@mmitche
Copy link
Member

mmitche commented Jan 24, 2025

Awesome!!!!

Copy link
Member

@mmitche mmitche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with minor tweak if necessary.

@ellahathaway ellahathaway enabled auto-merge (squash) January 24, 2025 22:22
@ViktorHofer
Copy link
Member

Will this break official builds until the linked issue is resolved? Or is the error just ignored?

@mmitche
Copy link
Member

mmitche commented Jan 24, 2025

When not all packages are signed, the validation stage is marked with a warning and an error message is outputted to the UI.

The stage warns currently

@ViktorHofer
Copy link
Member

This will make the official build longer again but I see that there isn't a great way to avoid that. Is the plan to add the "publish to bar and feeds" stage after this one and block on it being green or run it in parallel to this new stage? @mmitche

@mmitche
Copy link
Member

mmitche commented Jan 27, 2025

This will make the official build longer again but I see that there isn't a great way to avoid that. Is the plan to add the "publish to bar and feeds" stage after this one and block on it being green or run it in parallel to this new stage? @mmitche

We could add in parallel. No reason to block publishing. I do not expect that we will keep this stage on in all cases. I expect that most builds will eventually be unsigned and this step will be skipped.

@ellahathaway ellahathaway merged commit 5b5f415 into dotnet:main Jan 27, 2025
36 of 38 checks passed
@ellahathaway ellahathaway deleted the validate-signed-artifacts branch January 27, 2025 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable signing validation on shipping VMR outputs
3 participants