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

Jenkins: JUnit Plugin: publish results doesn't show trend report until successful build

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Jenkins: JUnit Plugin: publish results doesn't show trend report until successful build

      Occured on Jenkins ver. 1.642.3 using JUnit Plugin 1.19

      I’ve added a post build step “Publish jUnit test result report” (see screenshot) and run 30 builds. The builds all contain test results, but no test result trend appears in the project page (see screenshot).

      All my builds fail because the tests fail. I saw an old issue about failing builds not showing in trend https://issues.jenkins-ci.org/browse/JENKINS-1230, and tried forcing the tests to report success. As soon as I did, the trend report showed up. Some test tools, like pytest, report failure if any tests fail, so it would be preferred if the trend report showed up even for failures.

        Attachments

          Activity

          Hide
          robertloo Robert Loo added a comment -

          I get the same issue. I couldn't find the answer anywhere. Thanks for posting this.

          Show
          robertloo Robert Loo added a comment - I get the same issue. I couldn't find the answer anywhere. Thanks for posting this.
          Hide
          marcello_romani Marcello Romani added a comment -

          Thanks for reporting this, I still see the issue with these versions:

          Jenkins ver. 2.89.4

          JUnit Plugin 1.24

          Show
          marcello_romani Marcello Romani added a comment - Thanks for reporting this, I still see the issue with these versions: Jenkins ver. 2.89.4 JUnit Plugin 1.24
          Hide
          skisel Sergey Kisel added a comment -

          This seems to me very important bug (or missing feature) in case of having long-running pipelines which may not be promoted to be successful for quite a long time. If its CI/CD pipeline (Build -> Junit test -> promotion input -> staging deployment -> promotion input -> production deployment) when service is being promoted from staging environment to prod during 2 week scrum sprint cycle - its not very convenient to see trend only after 2 weeks.

           

          Show
          skisel Sergey Kisel added a comment - This seems to me very important bug (or missing feature) in case of having long-running pipelines which may not be promoted to be successful for quite a long time. If its CI/CD pipeline (Build -> Junit test -> promotion input -> staging deployment -> promotion input -> production deployment) when service is being promoted from staging environment to prod during 2 week scrum sprint cycle - its not very convenient to see trend only after 2 weeks.  

            People

            • Assignee:
              Unassigned
              Reporter:
              mmacvicar Mark MacVicar
            • Votes:
              6 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated: