Extracting artifacts out of our Travis builds to help debug failures / SauceLabs still needed?

Subject: Extracting artifacts out of our Travis builds to help debug failures / SauceLabs still needed?

From: Erik Huelsmann <..hidden..>

Date: Tue, 17 May 2016 13:27:24 +0200

Hi,

Last week, I was discussing with John how I have a local plugin for our BDD tests which generates screenshots pre- and post-step on *every* step in the BDD tests.

We were talking how it would be easy to have those screenshots extracted from our Travis builds; possibly to use them as input on next builds as well (to assure screen output stability).

The problem I raised was that we don't have online storage for the project (S3 is integrated with Travis, but the S3 free plan goes only for a year and only 2k PUT requests). So John said he might be able to sponsor this facility for the project. If I took him up on that, we should have a plan on what we want to extract from our builds (and possibly how long to retain it).

I'm currently thinking we want to extract the screenshots only. Do we have anything else that makes sense?

As soon as we have the extraction of screenshots from our builders, does it still make sense to have SauceLabs testing? I mean, that's basically the service they offer, right?

Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.

Robust and Flexible. No vendor lock-in.

------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j