peru/.travis.yml

language: python
python:
  - "3.3"
  - "3.4"
  - "3.5"
  - "nightly"
install:
  - pip install -r ./requirements-dev.txt
  - pip install coveralls
script:
  - ./test.py --with-coverage -v
after_success:
  cd tests && coveralls
create .travis.yml Tests should be passing in 3.4, but failing in 3.3 and 3.2. 2014-06-17 00:09:50 +00:00			`language: python`
			`python:`
			`- "3.3"`
			`- "3.4"`
add Python 3.5 to our Travis build 2015-10-07 15:09:05 +00:00			`- "3.5"`
add nightly Python to our Travis runs 2016-04-26 16:39:05 +00:00			`- "nightly"`
travis needs to install flake8 2014-06-17 00:41:26 +00:00			`install:`
remove third-party/ Summary: Remove the third-party/ directory and no longer rely on copies of dependencies in the repo. When needed, fetch dependencies normally. This can usually be accomplished via `pip install -r requirements.txt` or `pip install -r requirements-dev.txt`. Even though `peru.yaml` is gone, `.peru/` is still in `.gitignore`, because the tests check for untracked files and will detect `.peru/` as an error. Test Plan: Successfully ran tests locally and via Travis CI. Reviewers: jacko Reviewed By: jacko Differential Revision: https://phabricator.buildinspace.com/D145 2014-12-21 05:06:36 +00:00			`- pip install -r ./requirements-dev.txt`
make sure coveralls is installed on Travis Summary: I'm not sure if the Travis default configuration changed, but our latest builds haven't been updating Coveralls. Make sure the client is installed. Test Plan: Tried it on my own fork, the command seemed to work. Reviewers: sean Reviewed By: sean Differential Revision: https://phabricator.buildinspace.com/D181 2015-01-26 23:57:48 +00:00			`- pip install coveralls`
create validate_third_party.sh and add it to .travis.yml We would love to have peru fetch all of its own dependencies, but that leads us to a bootstrapping problem: We can't run peru until it's dependencies are present. To work around that, we define dependencies in peru.yaml, and we also check them in. That means we could get into a state where what's checked in doesn't match what's in peru.yaml, which could cause all sorts of trouble. To avoid that problem, create the validate_third_party.sh script. This runs a fresh sync of our peru.yaml and compares the result to what we have in the repo, to make sure they match. Run this as part of our Travis tests. The expected workflow is that commits that change peru.yaml should also commit the new third-party, or else they'll break this test. We're not including this in test.sh, because it's pretty slow if you don't have PERU_PLUGINS_CACHE set to something persistent. Running it in Travis should be enough. 2014-06-28 20:45:52 +00:00			`script:`
reimplement shared bash scripts in python Summary: We have peru.sh and peru.bat, and also test.sh and test.bat. Rather than maintaining both of those duplicates to support Windows, just reimplement them in Python. There's also validate-third-party.sh, but we never really use that on Windows. We can port it in a later diff if we feel like it. Test Plan: Check that tests actually fail after introducing a bug. (To make sure we're not actually testing the installed version instead of the repo version.) Check that the linter fails after dirtying up some code. Check that the untracked file test fails by creating a random file during tests. Reviewers: sean Reviewed By: sean Differential Revision: https://phabricator.buildinspace.com/D143 2014-12-18 23:12:14 +00:00			`- ./test.py --with-coverage -v`
coveralls support Summary: Integrate with coveralls.io. Reviewers: jacko Reviewed By: jacko Differential Revision: https://phabricator.buildinspace.com/D28 2014-07-21 22:29:21 +00:00			`after_success:`
fix the coveralls report Summary: Ever since the switch from `test.sh` to `test.py`, we've been generating the `.coverage` file inside `tests/`. Update `.travis.yml` to run `coveralls` in the right place. Also, handle the `--with-coverage` flag in a slightly more flexible way. Test Plan: Watch the build in my fork and make sure it looks like it's going to work. Reviewers: sean Reviewed By: sean Differential Revision: https://phabricator.buildinspace.com/D182 2015-01-27 00:20:08 +00:00			`cd tests && coveralls`