#browser-automation #continuous-integration ## Documentation entry points Entry points for setting everything up with GitHub for a Node.js app. - [Official documentation startpage](https://docs.travis-ci.com) - [Getting started tutorial](https://docs.travis-ci.com/user/tutorial/) - [JavaScript (with Node.js)](https://docs.travis-ci.com/user/languages/javascript-with-nodejs/) - [Build environments](https://docs.travis-ci.com/user/reference/overview/) - [Caching dependencies](https://docs.travis-ci.com/user/caching/) - Install [Chrome](https://docs.travis-ci.com/user/chrome) and/or [Firefox](https://docs.travis-ci.com/user/firefox/) - Advice on [GUI and Headless Browser Testing](https://docs.travis-ci.com/user/gui-and-headless-browsers/) ## Repository for experiments https://github.com/systemboogie/explore-travis ## Pull Request builds and branch builds When in a pull request, Travis per default [runs two builds]( https://docs.travis-ci.com/user/pull-requests/#double-builds-on-pull-requests): - Pull Request build: Merges the PR branch into master and then runs the build - Branch build: Runs the build directly on the PR branch If that does not match the desired behavior, here are some ideas on how to adjust it: - [How to configure Travis-CI to build pull requests & merges to master w/o redundancy](https://stackoverflow.com/questions/31882306/how-to-configure-travis-ci-to-build-pull-requests-merges-to-master-w-o-redunda) ## Third-party articles - [CircleCI vs Travis vs Jenkins](https://hackernoon.com/continuous-integration-circleci-vs-travis-ci-vs-jenkins-41a1c2bd95f5)