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

Match new CVSS score failure exit code on Dependency-Check v8 or higher #116

Merged
merged 2 commits into from
Jan 18, 2023

Conversation

guidojw
Copy link
Contributor

@guidojw guidojw commented Jan 16, 2023

In v8.0.0, the CVSS score failure exit code was changed from 1 to 15 (PR: jeremylong/DependencyCheck#4511), which is why this extension now fails instead of warns on these because it still expects an exit code of 1.

This PR adds support for this by comparing the exitCode with 1 if the input dependency-check version starts with [0-7]., and otherwise a 15.

@guidojw guidojw requested a review from a team as a code owner January 16, 2023 20:53
@guidojw guidojw changed the title Match new exitCode on v8 or higher Match new CVSS score failure exit code on Dependency-Check v8 or higher Jan 16, 2023
@guidojw
Copy link
Contributor Author

guidojw commented Jan 16, 2023

Hi @ejohn20, this extension not supporting the breaking change from v8 forces us to pin to v7.4.4. It would be greatly appreciated if this could be resolved in a timely manner.

@ejohn20 ejohn20 changed the base branch from main to develop January 18, 2023 19:29
@ejohn20 ejohn20 merged commit f0abdcd into dependency-check:develop Jan 18, 2023
@ejohn20
Copy link
Collaborator

ejohn20 commented Jan 18, 2023

Merging to the develop branch so I can test the dev version of the extension before releasing.

@ejohn20
Copy link
Collaborator

ejohn20 commented Jan 19, 2023

I'm unable to reproduce this in my demo pipelines. I have merged this and released in v6.1.0. Please verify that the fix is working as expected.

@guidojw guidojw deleted the fix/violation-exit-code branch January 19, 2023 12:55
@guidojw
Copy link
Contributor Author

guidojw commented Jan 19, 2023

It happened when setting warnOnCVSSViolation to true, not anymore as of v6.1.1 of this extension.
Thanks for the quick response!

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.

2 participants