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

distinguish test reports filed from different parts of workflow

    XMLWordPrintable

Details

    • Pipeline - July/August, Pipeline - December

    Description

      JUnit test result archiving can happen multiple times inside workflow, and currently there's no way to meaningfully distinguish multiple invocations.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-53362 Update documentation for junit Pipeline step return value

          • Major - Major loss of function.
          • Open
          is blocking

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-41031 in Junit reports wrong output is shown for tests with same name

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-45826 XUnit support for distinguishing test reports from different steps

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-35420 Realtime junit report to support Pipeline (was: throws ClassCastException when pipeline run)

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-41031 in Junit reports wrong output is shown for tests with same name

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-41855 Add an label to Junit test report in Pipeline

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-41710 Annotate test results with a test run name

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is related to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-26107 Allow stage to operate as a labelled block

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-48020 Warning log spam "[hudson.tasks.junit.CaseResult getRun] In getOwner(), suiteResult.getParent() is null."

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-26522 Annotated block/stage status

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-36932 Add a "matrix" step to workflow-basic-steps

          • Major - Major loss of function.
          • Resolved
          relates to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-46166 Distingush tests by stage and parallel

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-40986 Matrix structure for Declarative Pipeline

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-39353 Include filtering by class name when splitting tests

          • Major - Major loss of function.
          • Closed
          links to

          Web Link CloudBees Internal CD-185

          Web Link Mailing list

          Web Link pipeline-maven PR #82

          Web Link PR 64

          Web Link PR #76

          Web Link xunit PR #49

          mentioned in

          Page Loading...

          Activity

            Ascending order - Click to sort in descending order
            View 49 older comments
            sid_s Sid S added a comment -

            trejkaz, could you share your XSLT file or link to it?

            sid_s Sid S added a comment - trejkaz , could you share your XSLT file or link to it?
            trejkaz trejkaz added a comment -

            We don't use an XSLT yet because we're using Gradle's reports, which are already in the right format.

             

            trejkaz trejkaz added a comment - We don't use an XSLT yet because we're using Gradle's reports, which are already in the right format.  
            ottago Nicholas Klopfer-Webber added a comment -

            We had the same problem, but managed to work it out.

            When we started using a Jenkinsfile we copied this example, however this bypasses the code that keeps each run of tests independent.

            step([$class : 'JUnitResultArchiver', testResults: '**/build/test-results/**/*.xml'])

            What we now use and works is:

            junit testResults: '**/build/test-results/**/*.xml'
            ottago Nicholas Klopfer-Webber added a comment - We had the same problem, but managed to work it out. When we started using a Jenkinsfile we copied this example, however this bypasses the code that keeps each run of tests independent. step([$class : 'JUnitResultArchiver' , testResults: '**/build/test-results /**/ *.xml' ]) What we now use and works is: junit testResults: '**/build/test-results /**/ *.xml'
            mark_han Mark Han added a comment -

            I think there's still a problem where running a simple `./gradlew test` merges all tests into one section, even though there can be multiple flavors of tests run. Not sure if this is the case if we explicitly break up the flavors e.g. `./gradlew testDebug` Do we need to break up `./gradlew` commands between separate stages? 

            mark_han Mark Han added a comment - I think there's still a problem where running a simple `./gradlew test` merges all tests into one section, even though there can be multiple flavors of tests run. Not sure if this is the case if we explicitly break up the flavors e.g. `./gradlew testDebug` Do we need to break up `./gradlew` commands between separate stages? 
            jglick Jesse Glick added a comment -

            Do we need to break up ./gradlew commands between separate stages?

            Currently I am afraid you do.

            jglick Jesse Glick added a comment - Do we need to break up ./gradlew commands between separate stages? Currently I am afraid you do.

            People

              abayer Andrew Bayer
              kohsuke Kohsuke Kawaguchi
              Votes:
              35 Vote for this issue
              Watchers:
              65 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: