sourcecred/.travis.yml

language: node_js
node_js:
  - "8"
script: yarn test
notifications:
  email:
    recipients:
      - wchargin+travis-sourcecred@gmail.com
      - decentralion+travis-sourcecred@dandelion.io
    on_failure: always
Setup travis CI testing (#58) Observe that it passed on this commit, but failed builds [#2: Break Tests][2], [#3: Break Flow][3], and [#4: Break Prettier][4]. Close #23 [2]: https://travis-ci.org/sourcecred/sourcecred/builds/348453195 [3]: https://travis-ci.org/sourcecred/sourcecred/builds/348454983 [4]: https://travis-ci.org/sourcecred/sourcecred/builds/348455387 2018-03-02 14:39:54 -08:00			`language: node_js`
			`node_js:`
travis: pin Node v8.x.x (#867) Summary: SourceCred officially supports Node v8.x.x, so Travis should be testing against that version of Node. This fixes a cron-only, Travis-only failure. The test for the build script asserts that stderr only contains some known expected messages. On Node v10, which Travis was using, there is an additional deprecation message due to <https://github.com/yarnpkg/yarn/issues/5477>. Test Plan: To see that this fixes the current cron-only build failure, add the `--full` argument to the `test` script in `package.json`, and push the resulting tree to Travis. Note that it runs `sharness-full`, which passes. wchargin-branch: travis-node-8 2018-09-19 18:18:34 -07:00			`- "8"`
package.json: reorganize test commands (#571) Summary: Running `yarn test` (equiv. `npm test` or `npm run test`) now runs all checks. It takes the place of the former `yarn travis`. This is more in line with the expectation of a top-level `test` command: if it passes, your code is good. The `unit` command now runs Jest once, not in watch mode. It takes the place of the former `ci-test`. To run tests in watch mode, run any of the following: - `yarn unit --watch`, or - `npm run unit -- --watch`, or - `npm unit -- --watch`. This behavior is more consistent with the standard behavior of commands like `make test`. It is also empirically what @wchargin and @decentralion want most of the time. Test Plan: Verify that each of the scripts `test`, `unit`, and `coverage` passes. Verify that each of the aforementioned `--watch` invocations works. Verify that `.travis.yml` has the correct `script:` command. wchargin-branch: reorganize-test-command 2018-07-31 10:53:10 -07:00			`script: yarn test`
Ensure build failure emails (#339) When the cron build fails, we want to make sure that we know about it. This commit ensures that Travis emails @wchargin and @decentralion on any build failure; our email filters will ensure that cron job failures get noticed. Based on documentation at: https://docs.travis-ci.com/user/notifications 2018-06-04 14:52:07 -07:00			`notifications:`
			`email:`
			`recipients:`
travis: fix notification email config (#864) Summary: In #339, we attempted to configure Travis to email us on build failure. But we misread [the docs]: the emails need to be preceded by a hyphen. [the docs]: https://docs.travis-ci.com/user/notifications#configuring-email-notifications This is understandable because the Travis documentation renders the critical hyphen with `#999` against a background of `#f5f2f0` at 12px, which has a contrast ratio of only 2.55, failing WCAG 2.0 categorically. Test Plan: Fingers crossed. wchargin-branch: travis-email-config 2018-09-19 17:07:15 -07:00			`- wchargin+travis-sourcecred@gmail.com`
			`- decentralion+travis-sourcecred@dandelion.io`
Ensure build failure emails (#339) When the cron build fails, we want to make sure that we know about it. This commit ensures that Travis emails @wchargin and @decentralion on any build failure; our email filters will ensure that cron job failures get noticed. Based on documentation at: https://docs.travis-ci.com/user/notifications 2018-06-04 14:52:07 -07:00			`on_failure: always`