-
Notifications
You must be signed in to change notification settings - Fork 186
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
[JENKINS-57098] JSON Parser for Json report #177
Conversation
Codecov Report
@@ Coverage Diff @@
## master #177 +/- ##
============================================
+ Coverage 88.61% 88.64% +0.02%
- Complexity 1328 1339 +11
============================================
Files 163 165 +2
Lines 4216 4235 +19
Branches 464 465 +1
============================================
+ Hits 3736 3754 +18
Misses 323 323
- Partials 157 158 +1
Continue to review full report at Codecov.
|
@uhafner Thank you for merging this. |
I will add it, thanks for your work! |
See commit jenkinsci/warnings-ng-plugin@7063463 |
As discussed in #168 (comment) and the next comments, this PR organize JSON parser differently:
1.
JsonLogParser
(introduced asJsonParser
in #168)The format is a file (not
.xml
and not.json
) where each line is an issue serialized as separated JSON object.2.
JsonParser
Parse a JSON report produced by the "Jenkins Warnings Next Generation Plugin" with the API call:
GET [build-url]/[tool-id]/all/api/json
The format is json file (ending with
.json
) containing a valid JSON Object.This object as a member
issues
containing an array of issues. Example: