Skip to content

Latest commit

 

History

History
26 lines (18 loc) · 1.24 KB

continuous_integration.md

File metadata and controls

26 lines (18 loc) · 1.24 KB

Continuous Integration (CI)

We use Travis CI for continuous integration. Every time a pull request is opened or updated with more commits, a build is triggered.

It is a good idea to test your code locally before opening a pull request, so as to avoid failed builds and needing to revise the pull request. Use the following command to run the tests exactly as they are run by Travis CI:

./scripts/ci

Travis CI Configuration

  • We cache Bower and npm dependencies to speed up builds. The caches can be accessed on the web, which gives us a means to clear them in case they are spoiled (for example, by storing bad data in one of the cached directories).

  • You can validate the .travis.yml file before committing it to reduce common build errors. Travis has a convenient web-based tool where you can paste the contents of .travis.yml for validation.

  • You can skip a Travis CI build if a build is unnecessary for a particular commit.