forked from capability-boosters-dev/canvas-lms
-
Notifications
You must be signed in to change notification settings - Fork 0
/
docker-compose.jenkins.yml
48 lines (43 loc) · 1.45 KB
/
docker-compose.jenkins.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
version: "2"
# despite building upon the other docker-compose files, in CI land we only
# spin up things explicitly listed here. so to add a new service to CI,
# you need to at least add something here (it can as simple as
# `service_name: {}` if the upstream config is correct)
#
# if you have a service that depends on cached volume data (e.g. pre-
# migrated postgres, assets, etc), ensure it shares a volume with the
# data_loader, and it will automagically get cached/fetched
#
# if you have a service that takes a few moments to spin up (e.g.
# a database server), if you want to ensure it's actually up as
# part of docker-composing, you should implement /wait-for-it
services:
redis:
image: redis:alpine
ports:
- "${REDIS_PORT}:6379"
postgres:
build: ./build/docker-compose/postgres/$PGVERSION
environment:
MASTER_RUNNERS: $MASTER_RUNNERS
ports:
- "${PGPORT}:5432"
cassandra:
build: ./build/docker-compose/cassandra
environment:
CASSANDRA_START_RPC: 'true'
MASTER_RUNNERS: $MASTER_RUNNERS
volumes:
- cassandra_data:/var/lib/cassandra
ports:
- "${CASSANDRA_PORT}:9160"
data_loader:
build: ./build/docker-compose/data_loader
environment:
BASE_DOCKER_VOLUME_ARCHIVE: $BASE_DOCKER_VOLUME_ARCHIVE
DOCKER_CACHE_S3_REGION: $DOCKER_CACHE_S3_REGION
volumes:
- pg_data:/volumes/postgres_data
- cassandra_data:/volumes/cassandra_data
volumes:
cassandra_data: {}