zulip/.travis.yml

dist: trusty
before_install:
   - nvm install 0.10
install:
  - pip install coveralls
  - tools/travis/setup-$TEST_SUITE
  - tools/clean-venv-cache --travis
cache:
  - apt: false
  - directories:
    - $HOME/phantomjs
    - $HOME/zulip-venv-cache
    - node_modules
    - $HOME/node
env:
  global:
    - COVERALLS_PARALLEL=true
    - COVERALLS_SERVICE_NAME=travis-pro
    - COVERALLS_REPO_TOKEN=hnXUEBKsORKHc8xIENGs9JjktlTb2HKlG
    - BOTO_CONFIG=/tmp/nowhere
  matrix:
    - TEST_SUITE=frontend
    - TEST_SUITE=backend
language: python
python:
  - "2.7"
  - "3.4"
matrix:
  include:
    - python: "3.4"
      env: TEST_SUITE=static-analysis
    - python: "2.7"
      env: TEST_SUITE=production
      sudo: required
# command to run tests
script:
  - ./tools/travis/$TEST_SUITE
sudo: required
services:
- docker
addons:
  postgresql: "9.3"
after_success:
  coveralls
notifications:
  webhooks: https://coveralls.io/webhook?repo_token=$COVERALLS_REPO_TOKEN
Run tools/lint-all on Travis in python 3. 2016-07-02 03:06:57 +02:00			`dist: trusty`
Install node dependencies using npm. The node packages 'jQuery' and 'jquery' are different--'jQuery' is the legacy support package that is needed for Zulip so the require statements in the tests were updated. Travis uses node 4.0 by default and we are using 0.10, so the command to install the correct version had to be added to the .travis.yml file. 2015-10-26 17:16:26 +01:00			`before_install:`
travis: Cache the phantomjs package downloads between builds. This should hopefully fix the issue we've been seeing with bitbucket.org rejecting connections from Travis CI by not needing to connect to them. 2015-12-26 18:16:29 +01:00			`- nvm install 0.10`
Unrevert run Zulip tests automatically using Travis CI. This contains a fix written by nemeth from PR #63 for doing argument parsing properly. 2015-09-28 18:17:23 +02:00			`install:`
Generate mypy coverage report for travis + coveralls. 2016-06-04 21:03:14 +02:00			`- pip install coveralls`
Expand testing done via Travis CI to cover production pipeline. With this change, we are now testing the production static asset pipeline and installation process in a new testing job (and also run the frontend/backend tests separately). This means that changes that break the Zulip static asset pipeline or production installation process are more likely to fail tests. The testing is imperfect in that it does not have proper isolation -- we build a complete Zulip development environment and then install a Zulip production environment on top of it, so e.g. any apt dependencies installed for Zulip development will still be available for the Zulip production environment. But, it's better than nothing! A good v2 of this would be to have the production setup process just install the minimum stuff needed to run `build-release-tarball` and then uninstall it / clean it up so that we can do a more clear production installation, but that's more work. 2015-10-15 01:47:42 +02:00			`- tools/travis/setup-$TEST_SUITE`
Add code to clean the venv cache of old venvs. 2016-05-03 23:44:31 +02:00			`- tools/clean-venv-cache --travis`
Disable apt caching in Travis CI configuration. Apparently it isn't supposed to work reliably with the container-based infrastructure that we're using and empirically it's causing build failures. Thanks to @mijime for tracking this down. 2015-10-14 15:59:35 +02:00			`cache:`
			`- apt: false`
travis: Cache the phantomjs package downloads between builds. This should hopefully fix the issue we've been seeing with bitbucket.org rejecting connections from Travis CI by not needing to connect to them. 2015-12-26 18:16:29 +01:00			`- directories:`
Fix caching of install-phantomjs library in Travis CI. 2016-05-03 23:35:32 +02:00			`- $HOME/phantomjs`
Travis: Use /srv/zulip-venv-cache cache. 2016-05-03 22:54:29 +02:00			`- $HOME/zulip-venv-cache`
Cache node_modules in Travis. Fixes: #712 2016-06-02 11:54:05 +02:00			`- node_modules`
Cache npm for Travis CI. This should speed up all the major Zulip builds in Travis CI. Fixes #712. 2016-06-14 10:33:23 +02:00			`- $HOME/node`
Expand testing done via Travis CI to cover production pipeline. With this change, we are now testing the production static asset pipeline and installation process in a new testing job (and also run the frontend/backend tests separately). This means that changes that break the Zulip static asset pipeline or production installation process are more likely to fail tests. The testing is imperfect in that it does not have proper isolation -- we build a complete Zulip development environment and then install a Zulip production environment on top of it, so e.g. any apt dependencies installed for Zulip development will still be available for the Zulip production environment. But, it's better than nothing! A good v2 of this would be to have the production setup process just install the minimum stuff needed to run `build-release-tarball` and then uninstall it / clean it up so that we can do a more clear production installation, but that's more work. 2015-10-15 01:47:42 +02:00			`env:`
Generate mypy coverage report for travis + coveralls. 2016-06-04 21:03:14 +02:00			`global:`
			`- COVERALLS_PARALLEL=true`
			`- COVERALLS_SERVICE_NAME=travis-pro`
			`- COVERALLS_REPO_TOKEN=hnXUEBKsORKHc8xIENGs9JjktlTb2HKlG`
.travis.yml: Set BOTO_CONFIG to bogus value. See https://github.com/travis-ci/travis-ci/issues/5246. 2016-07-03 11:07:12 +02:00			`- BOTO_CONFIG=/tmp/nowhere`
Generate mypy coverage report for travis + coveralls. 2016-06-04 21:03:14 +02:00			`matrix:`
			`- TEST_SUITE=frontend`
			`- TEST_SUITE=backend`
Unrevert run Zulip tests automatically using Travis CI. This contains a fix written by nemeth from PR #63 for doing argument parsing properly. 2015-09-28 18:17:23 +02:00			`language: python`
			`python:`
			`- "2.7"`
Run frontend and backend tests in python3 on Travis. 2016-07-18 23:29:56 +02:00			`- "3.4"`
Add tools/run-mypy to Travis checks. Fixes #635. 2016-04-18 11:46:53 +02:00			`matrix:`
			`include:`
			`- python: "3.4"`
Merge mypy and py3k test suites in Travis. 2016-07-11 06:53:08 +02:00			`env: TEST_SUITE=static-analysis`
Run frontend and backend tests in python3 on Travis. 2016-07-18 23:29:56 +02:00			`- python: "2.7"`
			`env: TEST_SUITE=production`
Run tools/lint-all on Travis in python 3. 2016-07-02 03:06:57 +02:00			`sudo: required`
Unrevert run Zulip tests automatically using Travis CI. This contains a fix written by nemeth from PR #63 for doing argument parsing properly. 2015-09-28 18:17:23 +02:00			`# command to run tests`
			`script:`
Expand testing done via Travis CI to cover production pipeline. With this change, we are now testing the production static asset pipeline and installation process in a new testing job (and also run the frontend/backend tests separately). This means that changes that break the Zulip static asset pipeline or production installation process are more likely to fail tests. The testing is imperfect in that it does not have proper isolation -- we build a complete Zulip development environment and then install a Zulip production environment on top of it, so e.g. any apt dependencies installed for Zulip development will still be available for the Zulip production environment. But, it's better than nothing! A good v2 of this would be to have the production setup process just install the minimum stuff needed to run `build-release-tarball` and then uninstall it / clean it up so that we can do a more clear production installation, but that's more work. 2015-10-15 01:47:42 +02:00			`- ./tools/travis/$TEST_SUITE`
Unrevert run Zulip tests automatically using Travis CI. This contains a fix written by nemeth from PR #63 for doing argument parsing properly. 2015-09-28 18:17:23 +02:00			`sudo: required`
			`services:`
			`- docker`
			`addons:`
			`postgresql: "9.3"`
Generate mypy coverage report for travis + coveralls. 2016-06-04 21:03:14 +02:00			`after_success:`
			`coveralls`
			`notifications:`
			`webhooks: https://coveralls.io/webhook?repo_token=$COVERALLS_REPO_TOKEN`