-
Notifications
You must be signed in to change notification settings - Fork 3k
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
{ADO} Pin version 2.1.17
for cred scan
#21230
Conversation
Pin version for cred scan
2.1.17
for cred scan
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
ADO |
@@ -53,6 +53,7 @@ jobs: | |||
inputs: | |||
toolMajorVersion: V2 | |||
suppressionsFile: './scripts/ci/credscan/CredScanSuppressions.json' | |||
toolVersionV2: '2.1.17' |
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.
Also, as an FYI: https://docs.microsoft.com/en-us/azure/security/develop/security-code-analysis-overview
Not sure what will be the replacement of CredScan. |
Pin version for cred scan
* [Packaging] BREAKING CHANGE: Drop `jmespath-terminal` from docker image (#21206) * {Packaging} Fix CI job "Test Yum Package" by using `centos7` (#21207) * Update azure-pipelines.yml for Azure Pipelines (#21230) Pin version for cred scan Co-authored-by: Jiashuo Li <[email protected]>
Because package
Microsoft.Security.CredScan
in taskRun Credential Scanner
was upgraded from version2.1.17
to the new version2.2.7.8
, a large number of issues were scanned, resulting in CI blocking pipeline linkTherefore, pin the version of
Microsoft.Security.CredScan
to the last successfully version2.1.17
to avoid blocking CI