| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2013-08-28 | chore(travis): clean up the build output | Vojta Jina | |
| 2013-08-23 | chore(travis): clean up logs | Vojta Jina | |
| Forward SauceConnect logs and Karma debug logs into a file and print these files at the very end of a build. | |||
| 2013-08-13 | chore(sauce): use tunnel-identifier and ready-file only on Travis | Vojta Jina | |
| 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. | |||
| 2013-06-28 | chore: set up Sauce Labs with Travis | Vojta Jina | |
| 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. | |||
