-
Notifications
You must be signed in to change notification settings - Fork 2
/
.gitlab-ci.yml
64 lines (56 loc) · 1.7 KB
/
.gitlab-ci.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
# This file is a template, and might need editing before it works on your project.
# Official framework image. Look for the different tagged releases at:
# https://hub.docker.com/r/library/python
# Pick zero or more services to be used on all builds.
# Only needed when using a docker container to run your tests in.
# Check out: http://docs.gitlab.com/ce/ci/docker/using_docker_images.html#what-is-a-service
# This folder is cached between builds
# http://docs.gitlab.com/ce/ci/yaml/README.html#cache
# This is a basic example for a gem or script which doesn't use
# services such as redis or postgres
# To get Django tests to work you may need to create a settings file using
# the following DATABASES:
#
# DATABASES = {
# 'default': {
# 'ENGINE': 'django.db.backends.postgresql_psycopg2',
# 'NAME': 'ci',
# 'USER': 'postgres',
# 'PASSWORD': 'postgres',
# 'HOST': 'postgres',
# 'PORT': '5432',
# },
# }
#
# and then adding `--settings app.settings.ci` (or similar) to the test command
stages:
- test
python_test:
stage: test
image: python:3.6.5-stretch
services:
- postgres:latest
variables:
POSTGRES_DB: database_name
DATABASE_URL: "postgresql://postgres:postgres@postgres:5432/$POSTGRES_DB"
before_script:
- python -V
- pip install -r backend/requirements/testing.txt
script:
- cd backend && coverage run manage.py test --settings=prohealth.settings.testing
after_script:
- cd backend && coverage report
js_test:
image: node:10.1.0-stretch
stage: test
before_script:
- node -v
- npm -v
- cd frontend && npm install --dev
cache:
paths:
- frontend/node_modules/
script:
- npm install jest
- npm run build
- npm test