Saucelabs badge

[alessioalex]

Hey,

Is there any way I can get a badge for my project? I saw that I need to setup a build id or something (I searched through the saucelabs website) ..? However I didn't find anything on the zuul wiki.

Can somebody help me out?

Thanks

[defunctzombie]

I think saucelabs has badges but I am not sure where on their site they are :(

[cledev]

Hi @alessioalex . I just figured this out today. You can get the badges at https://docs.saucelabs.com/reference/status-images/ . But they will say "unknown" unless you run zuul through travis-ci. Travis provides that build id and whatnot.

[jessetane]

FYI you can set the environment variable yourself to work around this:

TRAVIS_BUILD_NUMBER=$RANDOM zuul -- test.js

Relevant source:

zuul/lib/zuul.js

Line 56 in ed04011

build: process.env.TRAVIS_BUILD_NUMBER,

Might be nice to fall back to something like process.env.BUILD_NUMBER for this / other non-travis use cases?

[dzcpy]

After tried many time, I have found the reason why saucelabs always shows an unknown barge even though all my tests has passed. Here is the reason from saucelabs' documentation:

All you have to do is add either markdown or HTML code to your GitHub README or project site that references your Sauce Labs username and access key, and annotate your tests with the REST or WebDriver API.

What we need here is to use saucelabs api to update the job with an 'passed' field to indicate whether the test has passed on client site and it must be updated explicitly during a separate API call.
And here is how karma-runner module did it:

See also: #288

[vvo]

@andyhu I have matrix badges working here: https://github.com/algolia/algoliasearch-helper-js with zuul, not sure what you mean?

[dzcpy]

Hi @vvo,
Thanks for replying. Here is my config file for zuul. I passed all tests on saucelabs but the badge is still unknown (I've managed to update those jobs through a script though).

[dzcpy]

And did you test it on travis-ci? Travis CI has an addon sauce_connect which seems automatically update the saucelabs job annotation after test, however if we are on a development server, it doesn't work. For my transliteration module I showed you above I even used travis-ci but not add sauce_connect addon, so it might be the reason why it doesn't update the job info. However if you check karma-saucelabs-luncher you can see even if you are not using travis-ci saucelabs' job annotation can be still correctly updated.
For more detailed description about the issue please check here:
#288

[vvo]

Yes we are using travis-ci. For faux-jax I still dunno why the badge is not showing, Ill reload tests.

Here's the travis yml for helper: https://github.com/algolia/algoliasearch-helper-js/blob/master/.travis.yml

[dzcpy]

Thanks for investigating this issue. I'm not sure why in your project it is working fine, but as per saucelabs documentation, for each tests the test launcher must call their api to update the jobs info. However I haven't seen in zuul's source code, there is such functionality

[niftylettuce]

@vvo did you ever figure out why it was cached/unknown? I have same issue and it seems like everyone else does - Sauce doesn't tell us why either, even on their official support thread thing... 🤦

[vvo]

Nope sorry.. good luck!