Separate security scan for frontend too #519
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Morendil
force-pushed
the
remove-trivy-from-front-build
branch
from
8f38898
to
6b5ad77
Compare
Separate security scan from build-and-push, so we can make it optional in CI; this was the case for the backend but frontend was overlooked…
Morendil
force-pushed
the
remove-trivy-from-front-build
branch
from
6b5ad77
to
dcb8f58
Compare
mjeammet
approved these changes
Nov 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Separate security scan from build-and-push, so we can make it optional in CI; this was the case for the backend but frontend was overlooked…
Trivy scans still occasionally fail for wrong reasons (but are still useful despite that).