treeherder/.travis.yml

192 строки
8.4 KiB
YAML
Исходник Обычный вид История

group: deprecated # work around travis issue with trusty image https://github.com/travis-ci/travis-ci/issues/6928
2013-06-25 18:00:48 +04:00
env:
2013-06-25 21:05:18 +04:00
global:
# Ensure the vendored libmysqlclient library can be found at run-time.
- LD_LIBRARY_PATH="$HOME/venv/lib/x86_64-linux-gnu:$LD_LIBRARY_PATH"
- BROKER_URL='amqp://guest:guest@localhost:5672//'
- DATABASE_URL='mysql://root@localhost/test_treeherder'
- ELASTICSEARCH_URL='http://127.0.0.1:9200'
- TREEHERDER_DJANGO_SECRET_KEY='secretkey-of-at-50-characters-to-pass-check-deploy'
matrix:
include:
# Each entry here creates another sub-job.
# Job 1: Linters
- env: python-linters
sudo: false
language: python
python: "2.7.11"
cache:
directories:
- ~/venv
before_install:
# Create a clean virtualenv rather than using the one given to us,
# to work around: https://github.com/travis-ci/travis-ci/issues/4873
- if [[ ! -f ~/venv/bin/activate ]]; then virtualenv -p python ~/venv; fi
- source ~/venv/bin/activate
- pip install --disable-pip-version-check --upgrade pip==8.1.1
install:
Bug 1213230 - Use pip 8's require-hashes feature instead of peep As of pip 8, peep has now been integrated into pip. Migrating from peep to this native feature has several advantages: * It avoids the complexity/learning curve of using a wrapper around pip. * It means we do not need to fork the official Heroku Python buildpack (which handles pip installation of requirements files) in order to use hash verification on Heroku. (Once the buildpack updates to pip 8.) * Omitted sub-dependencies result in install-time errors rather than the user discovering omissions at run-time. * pip's native caching is used, and all packages are installed in one pip invocation, so it's significantly faster. * It has better handling of errors and corner cases. Key facts about the native feature: * hash-checking mode is enabled if at least one hash is found in the requirements files passed to pip, or can be force enabled by passing `--requires-hashes` when running `pip install`. * Once enabled, hash-checking mode enforces that all packages: - are pinned to a specific version - have hashes listed - have all sub-dependencies specified * Older versions of pip will error out if either `--require-hashes` or the requirements file `--hash` syntax is used, meaning it's not possible to accidentally lose hash-checking protection if the pip used is older than expected. For more details, see: https://pip.pypa.io/en/stable/user_guide/#hash-checking-mode https://pip.pypa.io/en/stable/reference/pip_install/#hash-checking-mode The pip version on Travis and in the Vagrant virtualenv has been updated to 8.0.2 in bug 1241144, and the stage/prod virtualenv in bug 1241519. The Heroku Python buildpack pip was updated in bug 1241909. The requirements files hashes were ported using `peep port`, and then comments/URLs re-added by hand.
2016-01-20 19:22:54 +03:00
- pip install --disable-pip-version-check --require-hashes -r requirements/common.txt -r requirements/dev.txt
script:
- python lints/queuelint.py
- flake8 --show-source
- isort --check-only --diff --quiet
# Job 2: Nodejs UI tests
- env: ui-tests
sudo: false
language: node_js
node_js: "6.2.0"
cache:
# Note: This won't re-use the same cache as the linters job,
# since caches are tied to the language/version combination.
directories:
- node_modules
install:
- npm install
before_script:
# Required for Karma tests (http://docs.travis-ci.com/user/gui-and-headless-browsers/)
- export DISPLAY=:99.0
- sh -e /etc/init.d/xvfb start
script:
- grunt checkjs
- npm test
- ./node_modules/.bin/grunt build --production
# Job 3: Python Tests Chunk A
- env: python-tests-main
# Once mysql 5.6 is available on the container infra, we should switch back
# to it for its faster boot time, by setting `sudo: false`.
sudo: required
dist: trusty
language: python
python: "2.7.11"
cache:
directories:
- ~/venv
addons:
apt:
packages:
# Install mysql 5.6 since the default is v5.5.
- mysql-server-5.6
- mysql-client-core-5.6
- mysql-client-5.6
services:
- rabbitmq
- memcached
before_install:
- curl -sSo ~/elasticsearch.deb https://download.elastic.co/elasticsearch/release/org/elasticsearch/distribution/deb/elasticsearch/2.3.5/elasticsearch-2.3.5.deb && sudo dpkg -i ~/elasticsearch.deb
- sudo service elasticsearch start
- while ! curl localhost:9200 &>/dev/null; do sleep 1; done
- sudo cp puppet/files/mysql/my.cnf /etc/mysql/conf.d/treeherder.cnf
- sudo service mysql restart
# Create a clean virtualenv rather than using the one given to us,
# to work around: https://github.com/travis-ci/travis-ci/issues/4873
- if [[ ! -f ~/venv/bin/activate ]]; then virtualenv -p python ~/venv; fi
- source ~/venv/bin/activate
- pip install --disable-pip-version-check --upgrade pip==8.1.1
- ./bin/vendor-libmysqlclient.sh ~/venv
# Create the test database for `manage.py check --deploy`.
- mysql -u root -e 'create database test_treeherder;'
install:
Bug 1213230 - Use pip 8's require-hashes feature instead of peep As of pip 8, peep has now been integrated into pip. Migrating from peep to this native feature has several advantages: * It avoids the complexity/learning curve of using a wrapper around pip. * It means we do not need to fork the official Heroku Python buildpack (which handles pip installation of requirements files) in order to use hash verification on Heroku. (Once the buildpack updates to pip 8.) * Omitted sub-dependencies result in install-time errors rather than the user discovering omissions at run-time. * pip's native caching is used, and all packages are installed in one pip invocation, so it's significantly faster. * It has better handling of errors and corner cases. Key facts about the native feature: * hash-checking mode is enabled if at least one hash is found in the requirements files passed to pip, or can be force enabled by passing `--requires-hashes` when running `pip install`. * Once enabled, hash-checking mode enforces that all packages: - are pinned to a specific version - have hashes listed - have all sub-dependencies specified * Older versions of pip will error out if either `--require-hashes` or the requirements file `--hash` syntax is used, meaning it's not possible to accidentally lose hash-checking protection if the pip used is older than expected. For more details, see: https://pip.pypa.io/en/stable/user_guide/#hash-checking-mode https://pip.pypa.io/en/stable/reference/pip_install/#hash-checking-mode The pip version on Travis and in the Vagrant virtualenv has been updated to 8.0.2 in bug 1241144, and the stage/prod virtualenv in bug 1241519. The Heroku Python buildpack pip was updated in bug 1241909. The requirements files hashes were ported using `peep port`, and then comments/URLs re-added by hand.
2016-01-20 19:22:54 +03:00
- pip install --disable-pip-version-check --require-hashes -r requirements/common.txt -r requirements/dev.txt
script:
# Several security features in settings.py (eg setting HSTS headers) are conditional on
# 'https://' being in the site URL. In addition, we override the test environment's debug
# value so the tests pass. The real environment variable will be checked during deployment.
# Replace grep with `--fail-level WARNING` once we're using Django 1.10, since in
# previous versions an exit code of 1 is hard-coded to only ERROR and above:
# https://github.com/django/django/commit/287532588941d2941e19c4cd069bcbd8af889203
# The pipefail ensures exceptions during the command still cause the step to fail.
- set -o pipefail; SITE_URL='https://treeherder.dev' TREEHERDER_DEBUG='False' ./manage.py check --deploy 2>&1 | awk '/^WARNINGS/{err=1} {print} END{exit err}'
- py.test tests/ --runslow --ignore=tests/e2e/ --ignore=tests/etl/ --ignore=tests/log_parser/ --ignore=tests/webapp/
# Job 4: Python Tests Chunk B
- env: python-tests-e2e-etl-logparser
# Once mysql 5.6 is available on the container infra, we should switch back
# to it for its faster boot time, by setting `sudo: false`.
sudo: required
dist: trusty
language: python
python: "2.7.11"
cache:
directories:
- ~/venv
addons:
apt:
packages:
# Install mysql 5.6 since the default is v5.5.
- mysql-server-5.6
- mysql-client-core-5.6
- mysql-client-5.6
services:
- rabbitmq
- memcached
before_install:
- curl -sSo ~/elasticsearch.deb https://download.elastic.co/elasticsearch/release/org/elasticsearch/distribution/deb/elasticsearch/2.3.5/elasticsearch-2.3.5.deb && sudo dpkg -i ~/elasticsearch.deb
- sudo service elasticsearch start
- while ! curl localhost:9200 &>/dev/null; do sleep 1; done
- sudo cp puppet/files/mysql/my.cnf /etc/mysql/conf.d/treeherder.cnf
- sudo service mysql restart
# Create a clean virtualenv rather than using the one given to us,
# to work around: https://github.com/travis-ci/travis-ci/issues/4873
- if [[ ! -f ~/venv/bin/activate ]]; then virtualenv -p python ~/venv; fi
- source ~/venv/bin/activate
- pip install --disable-pip-version-check --upgrade pip==8.1.1
- ./bin/vendor-libmysqlclient.sh ~/venv
install:
Bug 1213230 - Use pip 8's require-hashes feature instead of peep As of pip 8, peep has now been integrated into pip. Migrating from peep to this native feature has several advantages: * It avoids the complexity/learning curve of using a wrapper around pip. * It means we do not need to fork the official Heroku Python buildpack (which handles pip installation of requirements files) in order to use hash verification on Heroku. (Once the buildpack updates to pip 8.) * Omitted sub-dependencies result in install-time errors rather than the user discovering omissions at run-time. * pip's native caching is used, and all packages are installed in one pip invocation, so it's significantly faster. * It has better handling of errors and corner cases. Key facts about the native feature: * hash-checking mode is enabled if at least one hash is found in the requirements files passed to pip, or can be force enabled by passing `--requires-hashes` when running `pip install`. * Once enabled, hash-checking mode enforces that all packages: - are pinned to a specific version - have hashes listed - have all sub-dependencies specified * Older versions of pip will error out if either `--require-hashes` or the requirements file `--hash` syntax is used, meaning it's not possible to accidentally lose hash-checking protection if the pip used is older than expected. For more details, see: https://pip.pypa.io/en/stable/user_guide/#hash-checking-mode https://pip.pypa.io/en/stable/reference/pip_install/#hash-checking-mode The pip version on Travis and in the Vagrant virtualenv has been updated to 8.0.2 in bug 1241144, and the stage/prod virtualenv in bug 1241519. The Heroku Python buildpack pip was updated in bug 1241909. The requirements files hashes were ported using `peep port`, and then comments/URLs re-added by hand.
2016-01-20 19:22:54 +03:00
- pip install --disable-pip-version-check --require-hashes -r requirements/common.txt -r requirements/dev.txt
script:
- py.test tests/e2e/ tests/etl/ tests/log_parser/ --runslow
# Job 5: Python Tests Chunk C
- env: python-tests-webapp
# Once mysql 5.6 is available on the container infra, we should switch back
# to it for its faster boot time, by setting `sudo: false`.
sudo: required
dist: trusty
language: python
python: "2.7.11"
cache:
directories:
- ~/venv
addons:
apt:
packages:
# Install mysql 5.6 since the default is v5.5.
- mysql-server-5.6
- mysql-client-core-5.6
- mysql-client-5.6
services:
- rabbitmq
- memcached
before_install:
- curl -sSo ~/elasticsearch.deb https://download.elastic.co/elasticsearch/release/org/elasticsearch/distribution/deb/elasticsearch/2.3.5/elasticsearch-2.3.5.deb && sudo dpkg -i ~/elasticsearch.deb
- sudo service elasticsearch start
- while ! curl localhost:9200 &>/dev/null; do sleep 1; done
- sudo cp puppet/files/mysql/my.cnf /etc/mysql/conf.d/treeherder.cnf
- sudo service mysql restart
# Create a clean virtualenv rather than using the one given to us,
# to work around: https://github.com/travis-ci/travis-ci/issues/4873
- if [[ ! -f ~/venv/bin/activate ]]; then virtualenv -p python ~/venv; fi
- source ~/venv/bin/activate
- pip install --disable-pip-version-check --upgrade pip==8.1.1
- ./bin/vendor-libmysqlclient.sh ~/venv
install:
- pip install --disable-pip-version-check --require-hashes -r requirements/common.txt -r requirements/dev.txt
script:
- py.test tests/webapp/ --runslow
2013-06-27 20:57:44 +04:00
notifications:
email:
on_success: never
on_failure: always
# Do not run these on the travis server at this time.
# The end to end tests require the service to be running, but travis can't
# start the service for us. So we would have to have the default point to
# a dedicated dev service instance that is reach-able by travis. However, we
# require /etc/hosts to have an entry at this point to reach our current dev
# server. So these tests should be run only locally for now.
# - karma start config/karma-e2e.conf.js --reporters=dots --browsers=Firefox