Plugin is not parsing log files

[kensykora]

We are running the latest version of SauceLabs plugin (v1.6.48) and using Bamboo v5.6.1 build 4410

I'm having an issue that's very similar to this one: https://support.saucelabs.com/entries/22184446-Sauce-Ondemand-plugin-in-Bamboo-does-not-show-results

Basically I have enabled the plugin for the job I am running in the "Miscellaneous" tab, and have verified that the log files are producing the lines that match the format you specified in the docs on SauceLabs:

Log Excerpt:

build   25-Sep-2014 15:18:00    Results               Top Level Tests
build   25-Sep-2014 15:18:00    -------               ---------------
build   25-Sep-2014 15:18:00    Passed                Website.Tests.UI.HomepageTests.can_browse_to_about_page
build   25-Sep-2014 15:18:00    [stdout] = 
build   25-Sep-2014 15:18:00    SauceOnDemandSessionID=47136dbd2922490d9949f7d15aa3fbd3 job-name=can_browse_to_about_page

However, when I check the "SauceLabs" tab for the job's build results, it doesn't pick up that anything's been run:

Here is a link to the test run: https://saucelabs.com/tests/47136dbd2922490d9949f7d15aa3fbd3 -- I've made it public. Can you help me troubleshoot why this isn't picking up?

[rossrowe]

Hi Ken, sorry for taking so long to respond to your issue. Would you be able to raise a support issue with Sauce Labs via support.saucelabs.com, and would you also be able to attach your Bamboo build output and Bamboo system log to the issue? We've previously found that Bamboo doesn't reliably make the complete build output available to the plugin.

A workaround would be to set a 'build' value in the desired capabilities using the value of the 'SAUCE_BAMBOO_BUILDNUMBER' environment variable. This should ensure that the correct build number gets set on your jobs, which is then referenced when the Sauce results tab is viewed.

[kensykora]

Sure, I can log a ticket. Can you clarify what you mean by setting a 'build' value in desired capabilities? I know capabilities are used for selecting agents but I'm unclear on how these can be dynamically set at runtime -- they are typically set statically in the plan configuration and definition.

[rossrowe]

Hi Ken, you can also populate the DesiredCapabilities with the key-value pairs listed on the Sauce Test Configuration page - this page also describes how you can set the build number

[kensykora]

Sorry I have been ignoring this, I am looking into this now.

[kensykora]

The workaround you suggested for setting build in desired capabilities worked like a charm. However, the interface isn't quite working right. See these screen shots below. Do you still want me to submit a ticket to your support?

[rossrowe]

Hi Ken, it's probably worthwhile to raise a support ticket for this one -
I'm not sure that this will be solely related to the Bamboo plugin, and
might instead be related to how the Javascript/HTML of the embedded report
works within Bamboo.

Cheers,

Ross

On Fri, Oct 31, 2014 at 9:35 AM, Ken Sykora notifications@github.com
wrote:

The workaround you suggested for setting build in desired capabilities
worked like a charm. However, the interface isn't quite working right. See
these screen shots below. Do you still want me to submit a ticket to your
support?

[image: screen shot 2014-10-30 at 5 33 07 pm]
https://cloud.githubusercontent.com/assets/64756/4853360/ff807242-6084-11e4-9995-4de04e202692.png
[image: screen shot 2014-10-30 at 5 33 14 pm]
https://cloud.githubusercontent.com/assets/64756/4853361/ff83792e-6084-11e4-851a-ca28d0ded180.png
[image: screen shot 2014-10-30 at 5 32 59 pm]
https://cloud.githubusercontent.com/assets/64756/4853358/ff7d7100-6084-11e4-8d00-ebcc59d760ad.png
[image: screen shot 2014-10-30 at 5 33 10 pm]
https://cloud.githubusercontent.com/assets/64756/4853357/ff7cd060-6084-11e4-843b-0a978a535f42.png
[image: screen shot 2014-10-30 at 5 32 44 pm]
https://cloud.githubusercontent.com/assets/64756/4853359/ff7e6f42-6084-11e4-89e7-5b2ed9204d03.png

—
Reply to this email directly or view it on GitHub
#15 (comment)
.

[kensykora]

Primary resolution to this issue was to declare the build capability when invoking the selenium driver and passing it the SAUCE_BAMBOO_BUILDNUMBER environment variable that the plugin sets.