-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 TSA tools #47876
Enable TSA tools #47876
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR enables additional TSA-related tooling in the source-build pipelines to ensure enhanced analysis is performed during builds.
- Enabled binskim analysis
- Enabled policheck verification
- Enabled TSA tooling
Let me know if we should port this over to dotnet/dotnet internally and do a build to make sure things work. |
To test this, I would recommend porting these changes to the VMR and pushing your branch to dnceng and then queuing the UB pipeline. |
https://dev.azure.com/dnceng/internal/_build/results?buildId=2671857&view=results Should we do the same for source-build and source-build-lite? |
It should only be necessary to do source-build-lite. I don't see the value in running across the entire matrix. |
Done - https://dev.azure.com/dnceng/internal/_build/results?buildId=2672444&view=results The first build passed most relevant stages, there was an unrelated failure in Pass2 build for one architecture, oddly others passed @ViktorHofer - https://dev.azure.com/dnceng/internal/_build/results?buildId=2671857&view=logs&j=287a7939-eab3-5c36-8f0e-00afcd687924&t=4fb25e12-6d48-5139-7a32-8d5e685a65d1&l=109
Looks to me like the tools are running -- however I don't think they are doing so to the full extent. For example - binskim is only seeing 3 files - I don't see Policheck running but I don't see that for runtime either. Going to see if I can find evidence of it running elsewhere. |
dotnet/source-build#4901 - Ideally we wouldn't need to use |
I think @wtgodbe fixed this recently. |
And for source-build-lite here are the relevant steps:
|
@mmitche @ViktorHofer @MichaelSimons
Looks like source-build pipelines still aren't running these. Will try to enable.