You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add BuildCheck run notifications to msbuild output, even if no checks failed.
Include package name in output so it can be tracked in case of malicious package.
This is recommendation from our security leaders. This shall increase discoverability and awareness what BuildChecks packages have had run during build, so user can easily detect abnormal or unexpected behavior.
@baronfel We have to design how to align this request with terminal logger minimal verbosity model. There were reasoning that since BuildCheck from CLI will be opt-in (mostly by CLI argument) and from practical point of view rare, we can afford to include this in summary - provided some buildcheck have had actually run.
The text was updated successfully, but these errors were encountered:
Add BuildCheck run notifications to msbuild output, even if no checks failed.
Include package name in output so it can be tracked in case of malicious package.
This is recommendation from our security leaders. This shall increase discoverability and awareness what BuildChecks packages have had run during build, so user can easily detect abnormal or unexpected behavior.
@baronfel We have to design how to align this request with terminal logger minimal verbosity model. There were reasoning that since BuildCheck from CLI will be opt-in (mostly by CLI argument) and from practical point of view rare, we can afford to include this in summary - provided some buildcheck have had actually run.
The text was updated successfully, but these errors were encountered: