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

Support Pretty JSON outputs in Docker Traceability API

XMLWordPrintable

      The current plugin version supports ram JSONs only. It would be great to support human-readable JSON outputs

          [JENKINS-28728] Support Pretty JSON outputs in Docker Traceability API

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Description Original: The current plugin version supports JSONs only. It would be great to add an XML format by adding an additional converter. New: The current plugin version supports ram JSONs only. It would be great to support human-readable JSON outputs
          Manuel Recena Soto made changes -
          Assignee New: Manuel Recena Soto [ recena ]
          Manuel Recena Soto made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Manuel Recena Soto added a comment -

          Here is pull request: https://github.com/jenkinsci/docker-traceability-plugin/pull/19

          I would prefer a different output format, but this was the simplest way.

          Manuel Recena Soto added a comment - Here is pull request: https://github.com/jenkinsci/docker-traceability-plugin/pull/19 I would prefer a different output format, but this was the simplest way.

          Tom FENNELLY added a comment -

          Is this really needed guys? Most/all REST client tools (e.g. Postman) pretty the responses for you (JSON/XML).

          Tom FENNELLY added a comment - Is this really needed guys? Most/all REST client tools (e.g. Postman) pretty the responses for you (JSON/XML).

          Oleg Nenashev added a comment -

          tfennelly, the browser does not do it by default. Jenkins REST API also uses a special parameter to output pretty JSONs

          Oleg Nenashev added a comment - tfennelly , the browser does not do it by default. Jenkins REST API also uses a special parameter to output pretty JSONs

          Tom FENNELLY added a comment -

          Hey Oleg (oleg_nenashev). Sure, the browser doesn't do it by default, but most of the time it's not humans reading the JSON so you don't care. Not a big deal but I think, in this day and age (with lots of nice REST client tools that do client side formatting + lots more), doing server side formatting seems bad to me coz it just adds more overhead on the server (formatting does add a fair bit of overhead in my experience). Not a biggie of course

          Tom FENNELLY added a comment - Hey Oleg ( oleg_nenashev ). Sure, the browser doesn't do it by default, but most of the time it's not humans reading the JSON so you don't care. Not a big deal but I think, in this day and age (with lots of nice REST client tools that do client side formatting + lots more), doing server side formatting seems bad to me coz it just adds more overhead on the server (formatting does add a fair bit of overhead in my experience). Not a biggie of course

          Manuel Recena Soto added a comment - - edited

          oleg_nenashev I understand this ticket does not make sense because its PR is inactive. What do you propose?

          Manuel Recena Soto added a comment - - edited oleg_nenashev I understand this ticket does not make sense because its PR is inactive. What do you propose?

          Oleg Nenashev added a comment -

          I think it's OK to keep both issue and PR open if you're planning to finish them at some point

          Oleg Nenashev added a comment - I think it's OK to keep both issue and PR open if you're planning to finish them at some point

            recena Manuel Recena Soto
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: