[JIRA] (JENKINS-55818) Extend REST API to enable navigation by modules, issue types, priority etc.

[sschlet (JIRA)]

Stefan Schletterer created an issue

Jenkins / JENKINS-55818 Extend REST API to enable navigation by modules, issue types, priority etc. Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-28 18:03 Priority: Minor Reporter: Stefan Schletterer The web gui of the static analysis plugin allows me to navigate and sort the data by modules, issue types and filter by severity. However, the io.jenkins.plugins.analysis.core.restapi.AnalysisResultApi }}doesn't return the required information to navigate e.g. to a specific module. Currently the only navigation path is for {{./new, ./fixed and ./all.    However, when using the web gui, and navigating to a specific module, then a URL is generated for this module, and this can be used to get the data RESTful for the module (like cppcheck/moduleName.192380630/api/json).    In our specific case we want to display say top 5 modules in a web dashboard, and allow the user to jump to the Jenkins warnings-ng UI, eg. <jenkins-job-url>job/cppCheck/14/cppcheck/moduleName.1853593734/type.1844850586/   Perhaps the tree query syntax enable sorting and paging like on the web ui. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[sschlet (JIRA)]

Stefan Schletterer updated an issue

Jenkins / JENKINS-55818 Extend REST API to enable navigation by modules, issue types, priority etc.

Change By: Stefan Schletterer The web gui of the static analysis plugin allows me to navigate and sort the data by modules, issue types and filter by severity. However, the {{*io.jenkins.plugins.analysis.core.restapi.AnalysisResultApi* }}doesn't return the required information to navigate e.g. to a specific module. Currently the only navigation path is for {{./new,}} .{{/fixed}} and {{./all. }}   However, when using the web gui, and navigating to a specific module, then a URL is generated for this module, and this can be used to get the data RESTful for the module (like {{*cppcheck/moduleName.192380630/ {{type.1844850586/}} api/json*). }}   In our specific case With the legacy plugin we want to display say top 5 modules in a web dashboard are currently displaying Warnings by level , and allow the user with hyperlinks to jump to the Jenkins warnings -ng UI, eg web ui . {{<jenkins-job-url>job/cppCheck/14/cppcheck/moduleName.1853593734/type.1844850586/}}     Perhaps   I would also appreciate the tree query syntax enable sorting and paging like on , so that it would be possible to retrieve one dataset with all the web ui. information needed (So that the AnalysisResultApi serves as an entry point, from which a tree down to the issues could be retrieved)

Add Comment

[sschlet (JIRA)]

Stefan Schletterer updated an issue

Jenkins / JENKINS-55818 Extend REST API to enable navigation by modules, issue types, priority etc. Change By: Stefan Schletterer

The web gui of the static analysis plugin allows me to navigate and sort the data by modules, issue types and filter by severity. However, the {{*io.jenkins.plugins.analysis.core.restapi.AnalysisResultApi* }}   doesn't return the required information to navigate e.g. to a specific module. Currently the only navigation path is for {{ ./new,}} .{{/fixed}} and {{./all. }}   However, when using the web gui, and navigating to a specific module, then a URL is generated for this module, and this can be used to get the data RESTful for the module (like {{*cppcheck/moduleName.192380630/ \

{{type.1844850586/}}api/json*). }}   With the legacy plugin we are currently displaying Warnings by level, with hyperlinks to the Jenkins warnings web ui.      I would also appreciate the tree query syntax, so that it would be possible to retrieve one dataset with all the information needed (So that the AnalysisResultApi serves as an entry point, from which a tree down to the issues could be retrieved)

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-55818 Extend REST API to enable navigation by modules, issue types, priority etc.

Change By: Ulli Hafner Labels: help-wanted

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner assigned an issue to Unassigned

Jenkins / JENKINS-55818 Extend REST API to enable navigation by modules, issue types, priority etc.

Change By: Ulli Hafner Assignee: Ulli Hafner

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-55818

Re: Extend REST API to enable navigation by modules, issue types, priority etc. I'm not sure if I misinterpret the requirement, but this is already possible. You can use the URL that you are using in the UI and simply add the api suffix. E.g.: http://localhost:8080/view/Dashboard/job/pipeline-analysis-model/66/cpd/packageName.-423259349/api/json. This will export only the filtered issues.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner resolved as Cannot Reproduce

Jenkins / JENKINS-55818

Extend REST API to enable navigation by modules, issue types, priority etc.

Change By: Ulli Hafner Status: Open Resolved Resolution: Cannot Reproduce

Add Comment