Fix influx counter for whitesource #5133
Open
Conversation
This file contains hidden or 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
|
|
tlefaix
force-pushed
the
fix/influx_whitesource
branch
from
1fa3287 to
c9b8832
Compare
tlefaix
force-pushed
the
fix/influx_whitesource
branch
from
c9b8832 to
a0a9aac
Compare
|
tlefaix
force-pushed
the
fix/influx_whitesource
branch
2 times, most recently
from
a26b45e to
13aa442
Compare
tlefaix
force-pushed
the
fix/influx_whitesource
branch
from
13aa442 to
073d90a
Compare
tlefaix
force-pushed
the
fix/influx_whitesource
branch
from
a0f7812 to
b6d5c1f
Compare
tlefaix
force-pushed
the
fix/influx_whitesource
branch
2 times, most recently
from
f7a4afd to
1629ef4
Compare
|
tlefaix
force-pushed
the
fix/influx_whitesource
branch
from
1629ef4 to
0e8707e
Compare
tlefaix
force-pushed
the
fix/influx_whitesource
branch
from
0e8707e to
3f907c6
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.
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.