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

API call results empty waring messages

    Details

    • Similar Issues:

      Description

      I have a build with checkstyle error message. The checkstyle.xml is produced by PHP_CodeSniffer.

      See from attached how that build looks on the web and in JSON response (the warnings are represented by {}), so it's known that warnings exist, but their messages are missing.

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          Maybe we should improve the inline documentation of the remote API with some examples. Currently there is just a note that the parameter tree is available...

          Show
          drulli Ulli Hafner added a comment - Maybe we should improve the inline documentation of the remote API with some examples. Currently there is just a note that the parameter tree is available...
          Hide
          danielbeck Daniel Beck added a comment -

          Ulli: The entire section "Controlling the amount of data you fetch" is about the tree parameter.

          Show
          danielbeck Daniel Beck added a comment - Ulli: The entire section "Controlling the amount of data you fetch" is about the tree parameter.
          Hide
          drulli Ulli Hafner added a comment -

          Ah, thanks. Didn't see that. Just noted the section in the top of the help about the JSON explanation ("Access the same data as JSON for JavaScript-based access. tree may be used."). Maybe we should link to the bottom here, too (like in the XML section). I stopped reading after the note with the link to the Wiki page with further information. I hope that other users are not as blind while reading

          Show
          drulli Ulli Hafner added a comment - Ah, thanks. Didn't see that. Just noted the section in the top of the help about the JSON explanation ("Access the same data as JSON for JavaScript-based access. tree may be used."). Maybe we should link to the bottom here, too (like in the XML section). I stopped reading after the note with the link to the Wiki page with further information. I hope that other users are not as blind while reading
          Hide
          aik099 Alexander Obuhovich added a comment -

          Fact, that "tree" parameter can be used in JSON was a surprise to me as well. Also nowhere mentioned that if you pass "*" instead of node name you get all content, e.g. "warnings[*]".

          Show
          aik099 Alexander Obuhovich added a comment - Fact, that "tree" parameter can be used in JSON was a surprise to me as well. Also nowhere mentioned that if you pass "*" instead of node name you get all content, e.g. "warnings [*] ".
          Hide
          danielbeck Daniel Beck added a comment -

          Yep, JENKINS-16395 was implemented in https://github.com/stapler/stapler/commit/bcb1ab27fa0751a0a9904e41107628f12c0c73c3 without corresponding documentation in Jenkins. I'll look into adding that.

          Show
          danielbeck Daniel Beck added a comment - Yep, JENKINS-16395 was implemented in https://github.com/stapler/stapler/commit/bcb1ab27fa0751a0a9904e41107628f12c0c73c3 without corresponding documentation in Jenkins. I'll look into adding that.

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              aik099 Alexander Obuhovich
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: