angular.js/lib/sauce, branch g3_v1_0 chore(sauce): use tunnel-identifier and ready-file only on Travis 2013-08-14T23:12:36+00:00 Vojta Jina 2013-08-13T04:29:20+00:00 cb89e02432d38b4310f691cfd0412cc55a4214c9 When running locally, there's not TRAVIS_JOB_NUMBER env variable defined and it screws the Sauce Connect (it uses a tunnel with empty name), this makes it work locally without defining TRAVIS_JOB_NUMBER env variable. Also, if you run the sauce_connect_setup.sh locally, without having SAUCE_CONNECT_READY_FILE, it does not pass the `--ready-file` argument to avoid Sauce Connect blowing up. 
When running locally, there's not TRAVIS_JOB_NUMBER env variable defined and it screws
the Sauce Connect (it uses a tunnel with empty name), this makes it work locally without defining
TRAVIS_JOB_NUMBER env variable.

Also, if you run the sauce_connect_setup.sh locally, without having SAUCE_CONNECT_READY_FILE, it
does not pass the `--ready-file` argument to avoid Sauce Connect blowing up.
chore: set up Sauce Labs with Travis 2013-06-28T23:36:30+00:00 Vojta Jina 2013-06-28T23:36:30+00:00 9a77d030471939464cd8ee1fb4b1af0a3532d799 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. 
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.