angular/angular.js

Setting env var `BROWSER_PROVIDER` to `browserstack` or `saucelabs`
determines which browser provider will be used.

This does not affect the build as all jobs are set to use SauceLabs.

Switch to Karma with Socket.io 1.x, which solves some issues(*) with BS.
Thus removing `config.transports` as it is not used anymore
(Socket.io 1.x starts with polling and tries to upgrade if available).

(*) folks from BS were fiddling with socket.io configuration to get it stable.
See dhimil/karma@4c04011
This is not necessary with Socket.io 1.x.

We’ve seen many failures recently because of Karma killing a browser
after browserNoActivityTimeout. It’s possible that this is not any issue
other than super slow network / proxy.

Will try higher timeout and observe for a while.

All of the recent failures were caused by too much load on SL, not
an actual problem.

I think a proper solution will be:
karma-runner/karma-sauce-launcher#37

For some reason, SL gives us Chrome 28 when no version is specified.

BREAKING CHANGE: As communicated before, IE8 is no longer supported.

more info: http://blog.angularjs.org/2013/12/angularjs-13-new-release-approaches.html

I think it's better to not specify the version as that should give the latest available version.
We should probably revert this commit at some point.

This might solve some flakiness on SL. At least Santi said that ;-)

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.

Because IE is retarded.

This is a terrible hack/workaround, however I don't think there is any better way to achieve this
with log4js.

This just improves the way BrowserStack groups the sessions.

I wanna see more info about BrowserStack...

Switch the build to use BrowserStack instead of SauceLabs.

This also adds IE11 to our build.

I still see some disconnection issues with IE9, hopefully this will help a bit.

Forward SauceConnect logs and Karma debug logs into a file and print these files at the very end of a build.

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

- 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.

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.

And also add shared config to make karma configs a bit simpler.