-
Notifications
You must be signed in to change notification settings - Fork 607
Fix influx counter for whitesource #5133
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
base: master
Are you sure you want to change the base?
Conversation
1fa3287
to
c9b8832
Compare
c9b8832
to
a0a9aac
Compare
|
a26b45e
to
13aa442
Compare
13aa442
to
073d90a
Compare
a0f7812
to
b6d5c1f
Compare
f7a4afd
to
1629ef4
Compare
|
1629ef4
to
0e8707e
Compare
0e8707e
to
3f907c6
Compare
|
Thank you for your contribution! This pull request is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add |
Changes
In case of several projects scanned (like with mta), collectVulnsAndLibsForProject (and therefore checkProjectSecurityViolations) will be called several times (see : https://github.com/SAP/jenkins-library/blob/master/cmd/whitesourceExecuteScan.go#L657)
Current issue is that in this case, the influx metrics will only contains the results for the latest scanned project.
Change is to accumulate values from each projects instead of replacing the values.
I also amended the existing tests to validate that influx metrics contains the correct value at the end.