mozilla
/
treeherder
зеркало из https://github.com/mozilla/treeherder.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
treeherder/.travis.yml

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

Bug 1137278 - Travis: Allow jobs to run on the new container based infra Travis have a newer container based stack that runs on EC2, that is both faster & allows the use of extra features (such as dependency caching): http://docs.travis-ci.com/user/workers/container-based-infrastructure/
2015-02-26 19:51:43 +03:00
sudo: false
add travis config file
2013-06-25 18:00:48 +04:00
language: python
python:
- "2.7"
Bug 1137278 - Travis: Cache the .cache/pip/ directory explicitly Travis |cache: pip| should do this for us, except it only works if we don't set our own install step, due to: https://github.com/travis-ci/travis-ci/issues/3239 Instead, let's manually specify the directory to cache.
2015-03-10 23:41:13 +03:00
cache:
directories:
Bug 1137278 - Travis: Re-use the virtualenv rather than the pip cache Whilst making Travis store the pip cache saves us from having to download the packages from PyPI each time, the vast majority of time spent during Travis run setup is compiling the packages that contain binary components. As such, let's try caching the virtualenv itself so we don't have to repeat this each time. We no longer get Travis to store the pip cache since it will only be used when the virtualenv is first created & will bloat the Travis cache archive that has to be downloaded from AWS at the start of each run.
2015-03-13 17:55:32 +03:00
- $HOME/virtualenv/python2.7.9
Bug 1166901 - Get the UI tests running as part of the travis run This merges the service and UI Travis configs, to get the Karma UI tests running on Travis in the new repo. We can only set 'language' to one value, however that doesn't matter, since nodejs is installed by default and all the 'language: node_js' did was set a few default build cycle steps - and we can define those ourselves manually. We install the deps using npm install, ensure they are cached by adding the node_modules directory to the cache list, get xvfb running for Karma (see http://docs.travis-ci.com/user/gui-and-headless-browsers/) and use |npm test| to run Karma using karma.conf.js. The end to end tests (karma-e2e.conf.js) are not currently running, same as before the repo merge.
2015-05-25 19:24:59 +03:00
- node_modules
add travis config file
2013-06-25 18:00:48 +04:00
env:
set travis env variables as global
2013-06-25 21:05:18 +04:00
global:
Bug 1175432 - Use dj-database-url to simplify DB environment variables dj-database-url extracts DB host, port, username, password and database name from the env variable 'DATABASE_URL' (unless another env variable name is specified). If the env variable is not defined, it falls back to the default passed to dj_database_url.config(). This means for Heroku and similar we can replace the multiple DB env variables with just one URL for default & one for read_only. This also effectively makes the setting of the read only DB variable mandatory for stage/production/heroku, since DEFAULT_DATABASE_URL won't be valid for them - so prevents us inadvertently not using the read only DB. The deployment script also had to be updated, so that we set the prod/stage-specific environment variables before using manage.py, since dj-database-url cannot rely on what's in the stage/prod local.py config (which isn't a bad thing, since we're deprecating that file).
2015-07-09 17:11:55 +03:00
- DATABASE_URL='mysql://root@localhost/treeherder'
- DATABASE_URL_RO='mysql://root@localhost/treeherder'
Bug 1199179 - Remove default Django SECRET_KEY Previously if TREEHERDER_DJANGO_SECRET_KEY was not set, we'd silently fall back to a default value for SECRET_KEY, meaning we wouldn't realise we were using an insecure key on a live deployment instance. With this change, TREEHERDER_DJANGO_SECRET_KEY being missing from the environment is fatal, resulting in: "ImproperlyConfigured: The SECRET_KEY setting must not be empty."
2015-08-27 15:04:12 +03:00
- TREEHERDER_DJANGO_SECRET_KEY='secretkey-1234'
add travis config file
2013-06-25 18:00:48 +04:00
services:
- rabbitmq
added memcached to the env
2013-11-21 04:59:42 +04:00
- memcached
add travis config file
2013-06-25 18:00:48 +04:00
install:
Bug 1166901 - Get the UI tests running as part of the travis run This merges the service and UI Travis configs, to get the Karma UI tests running on Travis in the new repo. We can only set 'language' to one value, however that doesn't matter, since nodejs is installed by default and all the 'language: node_js' did was set a few default build cycle steps - and we can define those ourselves manually. We install the deps using npm install, ensure they are cached by adding the node_modules directory to the cache list, get xvfb running for Karma (see http://docs.travis-ci.com/user/gui-and-headless-browsers/) and use |npm test| to run Karma using karma.conf.js. The end to end tests (karma-e2e.conf.js) are not currently running, same as before the repo merge.
2015-05-25 19:24:59 +03:00
- npm install
Bug 1169178 - Consolidate peep invocations There's no need to make multiple calls to peep - we can just combine them into one. Not changing the puppet instances for Vagrant, since the calls are made in two separate puppet modules and so would require a bit of refactoring, which is going to occur in bug 1074151 and friends.
2015-05-28 11:40:20 +03:00
- ./bin/peep.py install -r requirements/common.txt -r requirements/dev.txt
Bug 1137278 - Travis: Move the Cython build step to before_script The install step is usually only used for dependency installation. (The Travis build cycle is install -> before_script -> script)
2015-02-26 21:48:08 +03:00
before_script:
Bug 1143086 - Travis: Run flake8 first & end the job early if it fails Steps in before_script (and any other part of the build lifecycle apart from 'script') terminate the run immediately on failure. This means in the case of flake8 failures, the job changes from "in progress" to "errored" virtually immediately (with the virtualenv caching changes) so the user can see the problem and re-push straight away. See: http://docs.travis-ci.com/user/build-lifecycle/
2015-03-13 19:24:35 +03:00
- flake8 --show-source
Bug 1192957 - Add isort to the Travis run Any import style deviations will cause the Travis run to fail, with the diff output to the Travis log.
2015-09-22 00:06:58 +03:00
- isort --check-only --diff --quiet
Bug 1183367 - Add a grunt target to run eslint on JS frontend
2015-07-14 20:33:07 +03:00
- grunt checkjs
Bug 1166901 - Get the UI tests running as part of the travis run This merges the service and UI Travis configs, to get the Karma UI tests running on Travis in the new repo. We can only set 'language' to one value, however that doesn't matter, since nodejs is installed by default and all the 'language: node_js' did was set a few default build cycle steps - and we can define those ourselves manually. We install the deps using npm install, ensure they are cached by adding the node_modules directory to the cache list, get xvfb running for Karma (see http://docs.travis-ci.com/user/gui-and-headless-browsers/) and use |npm test| to run Karma using karma.conf.js. The end to end tests (karma-e2e.conf.js) are not currently running, same as before the repo merge.
2015-05-25 19:24:59 +03:00
# 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
Bug 1137278 - Travis: Move the Cython build step to before_script The install step is usually only used for dependency installation. (The Travis build cycle is install -> before_script -> script)
2015-02-26 21:48:08 +03:00
- mysql -e 'create database treeherder;'
add travis config file
2013-06-25 18:00:48 +04:00
script:
Bug 1166901 - Get the UI tests running as part of the travis run This merges the service and UI Travis configs, to get the Karma UI tests running on Travis in the new repo. We can only set 'language' to one value, however that doesn't matter, since nodejs is installed by default and all the 'language: node_js' did was set a few default build cycle steps - and we can define those ourselves manually. We install the deps using npm install, ensure they are cached by adding the node_modules directory to the cache list, get xvfb running for Karma (see http://docs.travis-ci.com/user/gui-and-headless-browsers/) and use |npm test| to run Karma using karma.conf.js. The end to end tests (karma-e2e.conf.js) are not currently running, same as before the repo merge.
2015-05-25 19:24:59 +03:00
- npm test
Bug 1133268 - Travis: Turn off code coverage checks The code coverage report isn't used anywhere & we'd be better off hooking coveralls.io or similar up to our repo instead.
2015-02-26 22:29:33 +03:00
- py.test tests/$* --runslow
Bug 1210546 - Run `grunt build` on Travis To ensure build script/parsing breakage is detected early.
2015-10-01 23:43:49 +03:00
- ./node_modules/.bin/grunt build --production
turn off travis notifications
2013-06-27 20:57:44 +04:00
notifications:
Bug 1140849 - Travis: Enable email notifications in the case of failures
2015-03-08 18:00:57 +03:00
email:
on_success: never
on_failure: always
Bug 1166901 - Get the UI tests running as part of the travis run This merges the service and UI Travis configs, to get the Karma UI tests running on Travis in the new repo. We can only set 'language' to one value, however that doesn't matter, since nodejs is installed by default and all the 'language: node_js' did was set a few default build cycle steps - and we can define those ourselves manually. We install the deps using npm install, ensure they are cached by adding the node_modules directory to the cache list, get xvfb running for Karma (see http://docs.travis-ci.com/user/gui-and-headless-browsers/) and use |npm test| to run Karma using karma.conf.js. The end to end tests (karma-e2e.conf.js) are not currently running, same as before the repo merge.
2015-05-25 19:24:59 +03:00
# 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