Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17767

Unable to get warnings from all parsers via API

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • warnings-plugin
    • Jenkins v1.512, Warnings plugins 4.52

    Description

      I'm looking for way to get list of warnings detected in particular build via API. I found out that there is API for each parser separately and they're distinguished by id (e.g /warnings32result/api/json). However I don't see any option to get all warnings or list of configured parsers.

      This is a bit blocking for me, as I'm creating tool that gathers build info from Jenkins.

      Attachments

        Issue Links

          Activity

            novakov Maciej Nowak created issue -
            novakov Maciej Nowak made changes -
            Field Original Value New Value
            Summary Unable to get warnings from all parsers Unable to get warnings from all parsers via API
            drulli Ulli Hafner made changes -
            Issue Type Bug [ 1 ] Improvement [ 4 ]
            Priority Major [ 3 ] Minor [ 4 ]
            drulli Ulli Hafner made changes -
            Link This issue is related to JENKINS-17780 [ JENKINS-17780 ]
            drulli Ulli Hafner made changes -
            Labels DEVTOOLS
            drulli Ulli Hafner made changes -
            Assignee Ulli Hafner [ drulli ] Sebastian Hansbauer [ habast ]
            drulli Ulli Hafner made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            drulli Ulli Hafner made changes -
            Link This issue is related to JENKINS-18852 [ JENKINS-18852 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 148947 ] JNJira + In-Review [ 192956 ]

            People

              habast Sebastian Hansbauer
              novakov Maciej Nowak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: