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

Embedded Sauce Report does not show up when session ID present in xunit file

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • sauce-ondemand-plugin
    • Sauce OnDemand Plugin v1.104
      Jenkins ver. 1.580.1
      browser: chrome
      language: python 2.7

      I am using RobotFramework and SauceLabs in my Jenkins job to do some automated testing. I am generating xunit reports with Robot and have it configured in such a way to log messages from stdout. Here is an example snippet of my xunit file:

      <system-out>
<![CDATA[
SauceOnDemandSessionID=93b1f4c98c2140108f97857326f9affe job-name=Some job name
]]>
</system-out>

      I have set up the post-build script to process this xunit file and I have checked the box for embedding the SauceLabs report. Despite all of this, I am getting this message in my console output:

      The Sauce OnDemand plugin is configured, but no session IDs were found in the test output

      I am completely stumped as to why it is not working. Any help with this issue would be greatly appreciated!

          [JENKINS-25435] Embedded Sauce Report does not show up when session ID present in xunit file

          Thomas Shewmake created issue -
          Oleg Nenashev made changes -
          Component/s New: sauce-ondemand-plugin [ 15751 ]
          Component/s Original: ci [ 18920 ]
          Key Original: INFRA-194 New: JENKINS-25435
          Project Original: Infrastructure [ 10301 ] New: Jenkins [ 10172 ]
          Workflow Original: jira [ 159388 ] New: JNJira [ 159402 ]
          Oleg Nenashev made changes -
          Assignee Original: R. Tyler Croy [ rtyler ] New: Kohsuke Kawaguchi [ kohsuke ]

          Oleg Nenashev added a comment -

          I suspect it's an issue for a Jenkins plugin => project = JENKINS
          INFRA project targets Jenkins backend infrastructure.

          Oleg Nenashev added a comment - I suspect it's an issue for a Jenkins plugin => project = JENKINS INFRA project targets Jenkins backend infrastructure.
          Ross Rowe made changes -
          Assignee Original: Kohsuke Kawaguchi [ kohsuke ] New: Ross Rowe [ rossrowe ]
          Ross Rowe made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Ross Rowe added a comment -

          My apologies for taking so long to respond to this issue, can you tell me if it's still a problem? If so, can you tell me if you have selected the 'Run Sauce Labs Test Publisher' post build action?

          Ross Rowe added a comment - My apologies for taking so long to respond to this issue, can you tell me if it's still a problem? If so, can you tell me if you have selected the 'Run Sauce Labs Test Publisher' post build action?

          Thomas Shewmake added a comment -

          Hi Ross,

          I was still able to reproduce the issue after some thorough investigation. I have also ensured that the "Run Sauce Labs Test Publisher" Post Build Action is enabled.

          Thomas Shewmake added a comment - Hi Ross, I was still able to reproduce the issue after some thorough investigation. I have also ensured that the "Run Sauce Labs Test Publisher" Post Build Action is enabled.

          Ross Rowe added a comment -

          Okay, thanks for letting me know, I'll try setup my environment to replicate the issue. As a workaround, can you try set the 'build' capability, using the value of the 'JENKINS_BUILD_NUMBER' environment variable? This should cause the Sauce job to be updated to include the Jenkins build number, which should in turn cause the Sauce jobs to appear within the build/test results.

          Ross Rowe added a comment - Okay, thanks for letting me know, I'll try setup my environment to replicate the issue. As a workaround, can you try set the 'build' capability, using the value of the 'JENKINS_BUILD_NUMBER' environment variable? This should cause the Sauce job to be updated to include the Jenkins build number, which should in turn cause the Sauce jobs to appear within the build/test results.

          Ross Rowe added a comment -

          Hi again, if you're using nosetest, would you be able to try add the -s argument to the command line? This should cause the output to be printed to Jenkins console log. If you're not using nosetest or you're still having issues, would you be able to attach your xunit xml file to this ticket so that I can run it through my environment (or you could raise a ticket via support.saucelabs.com, and attach the file to the ticket)

          Ross Rowe added a comment - Hi again, if you're using nosetest, would you be able to try add the -s argument to the command line? This should cause the output to be printed to Jenkins console log. If you're not using nosetest or you're still having issues, would you be able to attach your xunit xml file to this ticket so that I can run it through my environment (or you could raise a ticket via support.saucelabs.com, and attach the file to the ticket)

            rossrowe Ross Rowe
            tshewmake Thomas Shewmake
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: