chore(travis): force the latest version of selenium …
This might solve some flakiness on SL. At least Santi said that ;-)
chore(travis): switch back to SauceLabs …
I think we are pretty close to be able to use both. The xhr-polling seems to be pretty stable, but I'm having problems with multiple SSH tunnels (on BS), so let's try to switch back to SL.
chore(travis): ignore 404 warnings, debug log into file …
This is a terrible hack/workaround, however I don't think there is any better way to achieve this with log4js.
chore(travis): fix the build id on browser stack …
This just improves the way BrowserStack groups the sessions.
chore(travis): use only websockets and xhr-polling …
I wanna see more info about BrowserStack...
chore(travis): let's give BrowserStack a try …
Switch the build to use BrowserStack instead of SauceLabs. This also adds IE11 to our build.
chore(travis): increase disconnect timeout …
I still see some disconnection issues with IE9, hopefully this will help a bit.
chore(travis): clean up logs …
Forward SauceConnect logs and Karma debug logs into a file and print these files at the very end of a build.
chore: run more browsers on Travis (IE8,IE9,IE10,Safari,FF) …
Also instead of running everything in parallel, there are only two parallel tasks: - e2e tests running in the background (only on Chrome) - all the unit tests running sequentially
chore(travis): speed up the build …
- parallelize the tasks - cache requests (e2e tests) This reduces the time from ~18min to ~12min. It makes the output little messy. We could buffer output of each task and display it once it's fully finished, nicely. I think giving instant feedback is better.
chore: set up Sauce Labs with Travis …
This should not affect the Jenkins build at all. Now, the Travis build uses Chrome on Sauce Labs, which in theory gives us opportunity to use any browser/platform that Sauce Labs offers.
chore: update karma to 0.9.4 …
And also add shared config to make karma configs a bit simpler.