-
Notifications
You must be signed in to change notification settings - Fork 99
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
Add a step in the build pipeline to scan the grype/trivy results for issues #3133
Comments
Added a step but unfortunately GitHub doesn't have a nice way to preset optional steps: actions/runner#2347 End result: it runs, it fails but it's not visible in the pipeline unless you click on it. Also downloading the scan results from the pipeline artifacts, unzipping then an parsing them with a tool (e.g. sarif-tools) is a tedious job. Let's hope GitHub fixes the "Security" tab issue. |
Would be nice is we could use something like this: https://microsoft.github.io/sarif-web-component/ I'll do some research. Maybe there is an easy way to preset the scan results outside github. Update: It's open source: https://github.com/microsoft/sarif-web-component |
Scan results can be downloaded with one command:
|
Step was added. It's still not easy to consume but I don't see how it can be easily improved currently. |
Especially since the "Security" tab doesn't work very well.
The text was updated successfully, but these errors were encountered: