-
Notifications
You must be signed in to change notification settings - Fork 76
53 lines (51 loc) · 1.73 KB
/
s3-e2e.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
name: S3 E2E Tests
on: push
jobs:
s3-e2e:
timeout-minutes: 15
# TODO should we use the same container as circle & central?
runs-on: ubuntu-latest
services:
# see: https://docs.github.com/en/enterprise-server@3.5/actions/using-containerized-services/creating-postgresql-service-containers
postgres:
image: postgres:14.10
env:
POSTGRES_PASSWORD: odktest
ports:
- 5432:5432
# Set health checks to wait until postgres has started
options: >-
--health-cmd pg_isready
--health-interval 10s
--health-timeout 5s
--health-retries 5
minio:
# see: https://github.com/minio/minio/discussions/16099
image: minio/minio:edge-cicd
env:
MINIO_ROOT_USER: odk-central-dev
MINIO_ROOT_PASSWORD: topSecret123
# Enable encryption - this changes how s3 ETags work
# See: https://docs.aws.amazon.com/AmazonS3/latest/API/API_Object.html
# See: https://github.com/minio/minio/discussions/19012
MINIO_KMS_AUTO_ENCRYPTION: on
MINIO_KMS_SECRET_KEY: odk-minio-test-key:QfdUCrn3UQ58W5pqCS5SX4SOlec9sT8yb4rZ4zK24w0=
ports:
- 9000:9000
options: >-
--health-cmd "curl -s http://localhost:9000/minio/health/live"
--health-interval 10s
--health-timeout 5s
--health-retries 5
steps:
- uses: actions/checkout@v4
- name: Use Node.js 20
uses: actions/setup-node@v4
with:
node-version: 20.17.0
cache: 'npm'
- run: npm ci --legacy-peer-deps
- run: node lib/bin/create-docker-databases.js
- name: E2E Test
timeout-minutes: 10
run: ./test/e2e/s3/run-tests.sh