Skip to content
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

Feature/136 trivy integration #139

Merged
merged 61 commits into from
Jan 7, 2025
Merged

Conversation

alexander-dammeier
Copy link
Contributor

No description provided.

robertauer and others added 30 commits November 18, 2024 13:47
As trivy exits with exit code 1 when it encountered an error, we will use exit code 10 if trivy scanned successful and found vulnerabilities.
Also don't use RuntimeException, which is blocked by Jenkins.
To exclude CVEs from trivy scan, add a .trivyignore file to the
workspace.
The workspace is mounted to the docker container and therefore the
.trivyignore file is integrated into the scan process, if it exists
also update compiler dependencies
This reverts commit e6736d9.
The problem with this commit was, that now the jenkins pipeline
only creates empty jars. It only works on local machines when
we call our groovy tests directly
robertauer and others added 22 commits December 10, 2024 11:22
…es-build-lib into feature/136_trivy_integration
…integration

# Conflicts:
#	CHANGELOG.md
#	pom.xml
@meiserloh meiserloh merged commit 0d8cde4 into develop Jan 7, 2025
1 check was pending
@meiserloh meiserloh deleted the feature/136_trivy_integration branch January 7, 2025 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants