Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/.travis.yml

62 lines
1.4 KiB
YAML
Raw Normal View History

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:
provision: Use NVM to install node and npm. NVM takes a specific node version and installs the node package and a corresponding compatible npm package. We use it in a somewhat hackish way to install node/npm globally with a pinned version, since that's how we actually want to consume node in our development environment. Other details: - Travis CI now is configured to use the version of node installed by provision; the easiest way to do this was to sabotage the existing node installation. - jsdom is upgraded to a current version, which both requires recent node and also is required for the tests to pass with recent node. This fixes running the node tests on Xenial. Fixes #1498. [tweaked by tabbott]
2016-09-21 08:44:01 +02:00
# Disable Travis CI's built-in NVM installation
- mv ~/.nvm ~/.travis-nvm-disabled
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:
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:
Store coverage data under var/ tree. We set the COVERAGE_FILE environment variable which controls the output file path for the .coverage file produced by python-coverage, and also move the mypy coverage file to that location as well.
2016-08-07 06:32:24 +02:00
- COVERAGE_FILE=var/.coverage
Generate mypy coverage report for travis + coveralls.
2016-06-04 21:03:14 +02:00
- 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
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
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
travis-ci: add production Python 3 test suite. - Add production testing to .travis.yml file for PY3 env Fixes #1710.
2016-10-10 19:58:01 +02:00
- python: "3.4"
env: TEST_SUITE=production
Run frontend and backend tests in python3 on Travis.
2016-07-18 23:29:56 +02:00
- python: "2.7"
env: TEST_SUITE=production
travis: Restructure .travis.yml to be more consistent.
2017-02-12 20:06:31 +01:00
- python: "2.7"
env: TEST_SUITE=frontend
- python: "3.4"
env: TEST_SUITE=frontend
- python: "2.7"
env: TEST_SUITE=backend
- python: "3.4"
env: 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
# command to run tests
script:
travis: unset GEMPATH. Travis CI support suggested this as the correct solution for some recent changes in their environment that make ruby segfault.
2016-08-09 20:43:08 +02:00
- unset GEM_PATH
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:
Upload casper failure images to S3 in Travis. You need to define the following settings in Travis: - ARTIFACTS_KEY - ARTIFACTS_SECRET - ARTIFACTS_BUCKET - ARTIFACTS_REGION (if it's other than standard) Since we are uploading everything to S3 under `var/casper` this commit will also upload the server.log to S3. Fixes: #1263, Fixes: #1477
2016-09-22 10:29:31 +02:00
artifacts:
paths:
- $(ls var/casper/* | tr "\n" ":")
Upload test event log.
2016-09-30 12:35:49 +02:00
- $(ls /tmp/zulip-test-event-log/* | tr "\n" ":")
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
postgresql: "9.3"
Generate mypy coverage report for travis + coveralls.
2016-06-04 21:03:14 +02:00
after_success:
coveralls
notifications:
travis: Enable zulipbot build notifications. PRs labeled with the *travis updates* label will receive build notifications from zulipbot.
2017-03-11 20:36:24 +01:00
webhooks:
urls:
- https://coveralls.io/webhook?repo_token=$COVERALLS_REPO_TOKEN
- https://zulip.org/zulipbot/travis
on_success: always
on_failure: always