Support policy violations #269
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
sephiroth-j
force-pushed
the
feature/support-policy-violations
branch
from
481c967
to
bc86b40
Compare
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.
This includes a complete set of reports and charts: a new trend chart, a new summary chart and a new report page. But all in the same style as for the vulnerabilities.
The
VIEW_POLICY_VIOLATIONpermission is required to use this function.Unlike the vulnerabilities, there are no thresholds here. The only choice you have is to follow the defined rules and let a build become unstable on violations of the “WARN” status or let the build fail on violations of the “FAIL” status.
In the future, when Dependency-Track supports project policies (DependencyTrack/dependency-track#2130), marking a build as failed/unstable will probably be limited to project policies. Most certainly, however, the whole threshold feature will be removed as it should be replaced by project policies.