-
Notifications
You must be signed in to change notification settings - Fork 132
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
[VMR] Component Governance errors tracking #3152
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Just for book-keeping, the variables used to suppress the scans are following:
Present in following pipelines: |
So, we've got the Source Build I have also dismissed all of the multi-feed AzDO alerts based on https://dev.azure.com/dnceng/internal/_wiki/wikis/DNCEng%20Services%20Wiki/843/SingleFeedFAQ |
@brettfo we are seeing an alert in the VMR for this file: fsharp/tests/FSharp.Build.UnitTests/NuGet.Config which is synchronized from the I checked the history of the |
Ah, so it seems that we are probably fine to dismiss this as the root NuGet.config should be enough to functionally match copying the required feeds into the offending config. |
All critical and high alerts have been resolved so I am closing this now. I have also set up a weekly email that I get with a report of CG alerts for the VMR. |
NuGet problems
Plus there are more but once we sync the removal of
FileSystem
andCommon
submodules, they will go away.I think this one needs an exemption as it's a template for new projects
Missing root
NuGet.config
for some SB-infra projects #3230Missing root
NuGet.config
for some SB-infra projects #3230Missing root
NuGet.config
for some SB-infra projects #3230Missing root
NuGet.config
for some SB-infra projects #3230NPM problems
Issue to be created, I reached out to dougbu
Issue to be created, I reached out to dougbu
Issue to be created, I reached out to dougbu
Issue to be created, I reached out to dougbu
The text was updated successfully, but these errors were encountered: