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

TAP Plugin: yaml not displaying in extended test results

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: tap-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.609.1
      tap-plugin - latest (but shows 1.24)
    • Similar Issues:

      Description

      Any time simple yaml is included in the tap results, the TAP Extended Results shows raw html instead of a table.

      This works:

      TAP version 13
      1..4
      ok 1 JSHint | app.js: should pass jshint
      ok 2 JSHint | components/cars.js: should pass jshint
      not ok 3 JSHint | components/trucks.js: should pass jshint
      ok 4 JSHint | components/cycles.js: should pass jshint
      

      This does not (see attached picture of failure):

      TAP version 13
      1..4
      ok 1 JSHint | app.js: should pass jshint # skip this has known errors
      ok 2 JSHint | components/cars.js: should pass jshint # TODO uncomment the code
      not ok 3 JSHint | components/trucks.js: should pass jshint
        ---
          message: 'an error occured'
        ...
      ok 4 JSHint | components/cycles.js: should pass jshint
      

      I think I am using the download from 'latest', but it shows 1.24 in Jenkins. Maybe this is different than https://issues.jenkins-ci.org/browse/JENKINS-32729?

        Attachments

          Issue Links

            Activity

            Hide
            kinow Bruno P. Kinoshita added a comment -

            Always great when there are examples, specially a working and a bogus case. Trying to reproduce the issue.

            Show
            kinow Bruno P. Kinoshita added a comment - Always great when there are examples, specially a working and a bogus case. Trying to reproduce the issue.
            Hide
            kinow Bruno P. Kinoshita added a comment -

            The working example, works as expected. Attached screen shot.

            Show
            kinow Bruno P. Kinoshita added a comment - The working example, works as expected. Attached screen shot.
            Hide
            kinow Bruno P. Kinoshita added a comment -

            And the not working example, now works I believe I know the reason, but will investigate a bit before commenting. Attaching screen shot.

            Show
            kinow Bruno P. Kinoshita added a comment - And the not working example, now works I believe I know the reason, but will investigate a bit before commenting. Attaching screen shot.
            Hide
            kinow Bruno P. Kinoshita added a comment -

            Couldn't find exactly where it is being inserted, but I'm quite sure either Jenkins core, or one of our jelly files have:

            <?jelly escape-by-default='true'?>

            Which automatically escapes HTML, preventing XSS and also correctly rendering HTML in cases like the one described here.

            Show
            kinow Bruno P. Kinoshita added a comment - Couldn't find exactly where it is being inserted, but I'm quite sure either Jenkins core, or one of our jelly files have: <?jelly escape-by- default = ' true ' ?> Which automatically escapes HTML, preventing XSS and also correctly rendering HTML in cases like the one described here.
            Hide
            kinow Bruno P. Kinoshita added a comment -

            2.x should be working fine.

            Show
            kinow Bruno P. Kinoshita added a comment - 2.x should be working fine.

              People

              Assignee:
              kinow Bruno P. Kinoshita
              Reporter:
              sfbwalder Ben Walder
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: