peru/.travis.yml

language: python
python:
  - "3.2"
  - "3.3"
  - "3.4"
before_install:
  - sudo apt-get update -qq
install:
  - sudo apt-get install -qq realpath
  - pip install flake8
script:
  - ./test.sh
  - ./scripts/validate_third_party.sh
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.2"`
			`- "3.3"`
			`- "3.4"`
travis needs to install realpath 2014-06-17 00:20:58 +00:00			`before_install:`
			`- sudo apt-get update -qq`
travis needs to install flake8 2014-06-17 00:41:26 +00:00			`install:`
travis needs to install realpath 2014-06-17 00:20:58 +00:00			`- sudo apt-get install -qq realpath`
travis needs to install flake8 2014-06-17 00:41:26 +00:00			`- pip install flake8`
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:`
			`- ./test.sh`
			`- ./scripts/validate_third_party.sh`