Skip to content

Commit

Permalink
trivy: adds maven-invoker-plugin ignoring config
Browse files Browse the repository at this point in the history
Signed-off-by: Adrian Cole <[email protected]>
  • Loading branch information
Adrian Cole committed Feb 27, 2024
1 parent 7dcd132 commit a798864
Show file tree
Hide file tree
Showing 3 changed files with 17 additions and 0 deletions.
4 changes: 4 additions & 0 deletions build-bin/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,10 @@ On deploy:
On deploy_bom:
* The artifact `brave-bom` is deployed. Intentionally separate to allow a retry.

We also include a [Trivy configuration](trivy.yaml) which works around its lack
of support for maven-invoker-plugin. Run `./build-bin/trivy` from the project
root to get a vulnerability assessment.

[//]: # (Below here should be standard for all projects)

## Build Overview
Expand Down
6 changes: 6 additions & 0 deletions build-bin/trivy
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
#!/bin/sh -ue

# This script deploys a master or release version.
#
# See [README.md] for an explanation of this and how CI should use it.
trivy -c $(dirname "$0")/trivy.yaml repo .
7 changes: 7 additions & 0 deletions build-bin/trivy.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# As of Feb 2024, Trivy has no plans to handle maven-invoker-plugin.
# Skip to reduce noise about intentional tests against old versions.
# https://github.com/aquasecurity/trivy/discussions/5787
image:
skip-files:
- "**/src/it/*/pom.xml"
- "**/target/it/*/pom.xml"

0 comments on commit a798864

Please sign in to comment.