forked from buildkite/rails-docker-parallel-example
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathdocker-compose.yml
53 lines (49 loc) · 1.57 KB
/
docker-compose.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
version: '2'
services:
app:
build: .
links:
- db:db
- redis:redis
- memcache:memcache
# This mounts the current Buildkite build into /app, ensuring any
# generated files and artifacts are available to the buildkite-agent on
# the host machine (outside of the Docker Container)
volumes:
- "./:/app"
env_file:
- ".env-sample"
environment:
PGHOST: db
PGUSER: postgres
REDIS_URL: redis://redis
MEMCACHE_SERVERS: memcache
# CI envs
CI:
RAILS_ENV:
# CI envs For Knapsack Pro
BUILDKITE_PARALLEL_JOB:
BUILDKITE_PARALLEL_JOB_COUNT:
BUILDKITE_COMMIT:
BUILDKITE_BRANCH:
BUILDKITE_REPO:
BUILDKITE_BUILD_ID:
BUILDKITE_BUILD_NUMBER:
# if you want to configure Knapsack Pro with other ENVs
# you need to add them here to pass values to docker
KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC:
# For instance you can pass KNAPSACK_PRO_FIXED_QUEUE_SPLIT
# it should be defined to true if you use retry failed buildkite agent feature.
# Thanks to that you will be able to retry exactly the same tests as they were
# run on the failed agent.
# https://github.com/KnapsackPro/knapsack_pro-ruby#knapsack_pro_fixed_queue_split-remember-queue-split-on-retry-ci-node
# KNAPSACK_PRO_FIXED_QUEUE_SPLIT:
ports:
- "5000:5000"
entrypoint: wait-for-it.sh db:5432 -s -- wait-for-it.sh redis:6379 -s -- wait-for-it.sh memcache:11211 -s --
db:
image: postgres
redis:
image: redis
memcache:
image: tutum/memcached