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.

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

Enable binskim in the staging pipeline as part of the SDL runs "Source Code Validation" stage. #2662

Closed
Tracked by #2647
andriipatsula opened this issue Jun 15, 2023 · 1 comment
Assignees
Labels
area-product-construction Issues owned by the Product Construction team. Used to label epics and untriaged, loose issues. area-staging-pipeline Issues related to the staging part of the .NET release infrastructure.

Comments

@andriipatsula
Copy link
Member

andriipatsula commented Jun 15, 2023

  • Try to run Test Staging pipeline with binskim enabled and see what will happen
  • Rename the "Source Code Validation" stage to something more ~ "SDL and Loc Validation"

Q.: add support for baseline parameter?

@andriipatsula andriipatsula self-assigned this Jun 15, 2023
@andriipatsula andriipatsula changed the title Enable binskim in the staging pipeline (Stage-DotNet) as part of the SDL runs (the "Source Code Validation" stage). Enable binskim in the staging pipeline as part of the SDL runs "Source Code Validation" stage. Jun 15, 2023
@andriipatsula andriipatsula added area-product-construction Issues owned by the Product Construction team. Used to label epics and untriaged, loose issues. area-staging-pipeline Issues related to the staging part of the .NET release infrastructure. labels Jun 15, 2023
@andriipatsula
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-product-construction Issues owned by the Product Construction team. Used to label epics and untriaged, loose issues. area-staging-pipeline Issues related to the staging part of the .NET release infrastructure.
Projects
None yet
Development

No branches or pull requests

1 participant