pywb/.travis.yml

language: python

python:
  - "2.7"
  - "3.5"
  - "3.6"

os:
  - linux

addons:
  apt:
    packages:
      # This is required to run new chrome on old trusty
      - libnss3

env:
  - WR_TEST=no
  - WR_TEST=yes

addons:
  sauce_connect: true

cache:
  directories:
    - $HOME/.cache/pip
    - node_modules

sudo: true

install:
  - ./.travis/install.sh

before_script:
  - export DISPLAY=:99.0
  - sh -e /etc/init.d/xvfb start

script:
  - ./.travis/test.sh

after_success:
  - codecov

matrix:
  exclude:
    - env: WR_TEST=yes
      python: "2.7"
    - env: WR_TEST=yes
      python: "3.5"
add .travis.yml for Travis CI! 2014-01-23 16:20:51 -08:00			`language: python`
cleanup .travis.yml, remove lxml 2014-08-06 14:01:59 -07:00
add .travis.yml for Travis CI! 2014-01-23 16:20:51 -08:00			`python:`
fixes for 2.6 and pypy 2014-03-04 18:49:36 -08:00			`- "2.7"`
proxy: ensure proxy cert download sets content length proxy options: 'use_default_coll' must specify exact default coll (otherwise a random coll is chosen, as ordering is not defined) travis: add py3.4, py3.5! 2016-02-23 18:09:09 -08:00			`- "3.5"`
build: update gevent, support py3.6 2017-03-09 11:59:54 -08:00			`- "3.6"`
cleanup .travis.yml, remove lxml 2014-08-06 14:01:59 -07:00
travisci: experiment with travis improvements (new container build) 2014-12-23 12:39:33 -08:00			`os:`
			`- linux`
Add configuration for running client tests using Sauce Labs This gives us the capability to test the client-side JS rewriting against a suite of different browsers on different platforms. Note that getting Karma running on Travis CI requires some additional configuration documented at github.com/karma-runner/karma-sauce-launcher/issues/73 which is not made clear in the original documentation. In order to run the Karma tests, the Sauce Labs username and access keys need to be passed in via the SAUCE_USERNAME and SAUCE_ACCESS_KEYS env vars. 2015-11-25 12:18:56 +00:00
New integration tests using webrecorder-tests: (#355) New integration tests using webrecorder-tests: - WR_TEST=true is set for integration test run (only run with py3.6, excluded for py2.7, 3.5) - Added .travis directory that includes two scripts: install.sh and test.sh. - install.sh handles all installation and test.sh handles running of unit or integration tests - sudo: true required to run headless chrome 2018-07-09 16:21:14 -04:00			`addons:`
			`apt:`
			`packages:`
			`# This is required to run new chrome on old trusty`
			`- libnss3`

			`env:`
			`- WR_TEST=no`
			`- WR_TEST=yes`

Enable Sauce Connect in Travis Rather than specifying the username and encrypted key in the Travis config, we just enable Sauce Connect and require SAUCE_USERNAME and SAUCE_ACCESS_KEY env vars to be set. This is so that the Karma tests have the same env vars available to them which they can use to check whether to run against Sauce Labs or not. 2015-11-26 11:07:07 +00:00			`addons:`
			`sauce_connect: true`

Add Python and node_module caching Speed up Travis CI rebuilds by caching pip and npm dependencies. 2015-11-25 12:49:59 +00:00			`cache:`
			`directories:`
			`- $HOME/.cache/pip`
			`- node_modules`
travisci: experiment with travis improvements (new container build) 2014-12-23 12:39:33 -08:00
New integration tests using webrecorder-tests: (#355) New integration tests using webrecorder-tests: - WR_TEST=true is set for integration test run (only run with py3.6, excluded for py2.7, 3.5) - Added .travis directory that includes two scripts: install.sh and test.sh. - install.sh handles all installation and test.sh handles running of unit or integration tests - sudo: true required to run headless chrome 2018-07-09 16:21:14 -04:00			`sudo: true`
travisci: experiment with travis improvements (new container build) 2014-12-23 12:39:33 -08:00
add .travis.yml for Travis CI! 2014-01-23 16:20:51 -08:00			`install:`
New integration tests using webrecorder-tests: (#355) New integration tests using webrecorder-tests: - WR_TEST=true is set for integration test run (only run with py3.6, excluded for py2.7, 3.5) - Added .travis directory that includes two scripts: install.sh and test.sh. - install.sh handles all installation and test.sh handles running of unit or integration tests - sudo: true required to run headless chrome 2018-07-09 16:21:14 -04:00			`- ./.travis/install.sh`
cleanup .travis.yml, remove lxml 2014-08-06 14:01:59 -07:00
Configure Travis to make Firefox available for Karma tests For some Karma tests, we can run them faster by running against a local browser in the Travis CI instance rather than Sauce Labs. This is also useful for: - Contributors wishing to run the Travis tests against their own forks and have not set up Sauce Labs credentials. - Running Karma tests against Pull Request builds where Sauce Connect is not available. 2015-11-26 10:27:37 +00:00			`before_script:`
			`- export DISPLAY=:99.0`
			`- sh -e /etc/init.d/xvfb start`

travisci: experiment with travis improvements (new container build) 2014-12-23 12:39:33 -08:00			`script:`
New integration tests using webrecorder-tests: (#355) New integration tests using webrecorder-tests: - WR_TEST=true is set for integration test run (only run with py3.6, excluded for py2.7, 3.5) - Added .travis directory that includes two scripts: install.sh and test.sh. - install.sh handles all installation and test.sh handles running of unit or integration tests - sudo: true required to run headless chrome 2018-07-09 16:21:14 -04:00			`- ./.travis/test.sh`
testing coveralls 2014-02-24 23:43:32 -08:00
			`after_success:`
Add CodeCov (#282) coverage: switch coverage reporting to codecov, enable in travis-ci and appveyor coverage: update .coveragerc to include branch, exclude NotImplementedError, __repr__ README: badge update, add appveyor, codecov badges 2018-01-17 09:59:51 -08:00			`- codecov`

New integration tests using webrecorder-tests: (#355) New integration tests using webrecorder-tests: - WR_TEST=true is set for integration test run (only run with py3.6, excluded for py2.7, 3.5) - Added .travis directory that includes two scripts: install.sh and test.sh. - install.sh handles all installation and test.sh handles running of unit or integration tests - sudo: true required to run headless chrome 2018-07-09 16:21:14 -04:00			`matrix:`
			`exclude:`
			`- env: WR_TEST=yes`
			`python: "2.7"`
			`- env: WR_TEST=yes`
			`python: "3.5"`