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

Test message not show

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • tap-plugin
    • None

      I have this tap results from my tests (report.tap in attachment)

      • if I open TAP Extended Test Results and click on link near by File-Content I got error "Couldn't locate attachment in YAMLish: .tests/report.tap"
      • if I open TAP Test Results and click on test name I got 404

        1. ExtResults-1.png
          ExtResults-1.png
          103 kB
        2. ExtResults-2.png
          ExtResults-2.png
          3 kB
        3. report.tap
          3 kB
        4. Results-1.png
          Results-1.png
          91 kB
        5. Results-2.png
          Results-2.png
          6 kB
        6. Screenshot_2016-08-26_21-39-48.png
          Screenshot_2016-08-26_21-39-48.png
          109 kB
        7. Screenshot_2016-08-26_21-39-59.png
          Screenshot_2016-08-26_21-39-59.png
          78 kB
        8. Screenshot from 2016-08-26 21-40-10.png
          Screenshot from 2016-08-26 21-40-10.png
          93 kB

          [JENKINS-19602] Test message not show

          Bruno P. Kinoshita added a comment -

          Hi forrest79,

          I believe this issue has also been fixed a few releases ago, while fixing security problems with attachments and also with test results URLs.

          I've tried with the following scenario:

          1. Download report.tap to ~/Downloads
          2. Created a job with the following shell build step:

          cp /home/kinow/Downloads/report.tap .
touch report.tap

          3. Added a post build step for TAP, that included the report.tap

          I can successfully open the attachment.

          One thing I noticed is that there is another URL that is 404 for me now, because it's using the artifact URL, but since files are not always archived, it would be better to point to the workspace (which could have been removed, but that's OK).

          Bruno P. Kinoshita added a comment - Hi forrest79 , I believe this issue has also been fixed a few releases ago, while fixing security problems with attachments and also with test results URLs. I've tried with the following scenario: 1. Download report.tap to ~/Downloads 2. Created a job with the following shell build step: cp /home/kinow/Downloads/report.tap . touch report.tap 3. Added a post build step for TAP, that included the report.tap I can successfully open the attachment. One thing I noticed is that there is another URL that is 404 for me now, because it's using the artifact URL, but since files are not always archived, it would be better to point to the workspace (which could have been removed, but that's OK).

          Bruno P. Kinoshita added a comment -

          Actually, with pipelines in special, there are more cases where a workspace is not always available... specially if you have several slaves, and have to recall space for any reason.

          So will leave the code as is. But it was a digression, nothing really related to the issue So closing as fixed.

          Bruno P. Kinoshita added a comment - Actually, with pipelines in special, there are more cases where a workspace is not always available... specially if you have several slaves, and have to recall space for any reason. So will leave the code as is. But it was a digression, nothing really related to the issue So closing as fixed.

          Bruno P. Kinoshita added a comment -

          2.0.1 released

          Bruno P. Kinoshita added a comment - 2.0.1 released

            kinow Bruno P. Kinoshita
            forrest79 Jakub Trmota
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: