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

distinguish test reports filed from different parts of workflow

    Details

    • Sprint:
      Pipeline - July/August, Pipeline - December
    • Similar Issues:

      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

            Activity

            Hide
            sid_s Sid S added a comment -

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

            Show
            sid_s Sid S added a comment - trejkaz , could you share your XSLT file or link to it?
            Hide
            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.

             

            Show
            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.  
            Hide
            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'
            
            Show
            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'
            Hide
            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? 

            Show
            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? 
            Hide
            jglick Jesse Glick added a comment -

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

            Currently I am afraid you do.

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

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: