angular.js/lib/sauce, branch v1.2.5 chore(scripts): refactor travis scripts 2013-12-11T18:12:18+00:00 Vojta Jina 2013-12-11T17:56:06+00:00 8864e54f1f94883f3e22d7ce7ed87a699467a217 Refactoring so that it's easier to use both SL/BS just depending on a global switch. 
Refactoring so that it's easier to use both SL/BS just depending on a global switch.
 chore(travis): clean up the build output 2013-08-28T22:46:19+00:00 Vojta Jina 2013-08-28T19:09:13+00:00 4138a80611bb7c74d0ac002d7220f99d03a08a59 






chore(travis): clean up logs
2013-08-23T23:49:10+00:00

Vojta Jina

2013-08-21T10:16:57+00:00

80d0f98263786ef302ca7551c4515560a7c07195

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





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







chore(sauce): use tunnel-identifier and ready-file only on Travis
2013-08-14T06:02:21+00:00

Vojta Jina

2013-08-13T04:29:20+00:00

c6ca827150fd98ffba3245e93f1245bdc07887b1

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-28T18:43:38+00:00

Vojta Jina

2013-06-25T20:50:45+00:00

33223e26a0c6e73bddbc112829f35f373f97b10d

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.