-
Notifications
You must be signed in to change notification settings - Fork 11
300 lines (273 loc) · 10.8 KB
/
test-and-deploy.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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
name: Test and deploy
on: [ push, pull_request ]
env:
# Version required to run itwêwina:
ACTIONS_PYTHON_VERSION: '3.10'
# Version required to run npm build:
ACTIONS_NODE_VERSION: 22
jobs:
# Originally, it skipped deploy if [skip deploy] is present in the commit message.
# There is currently a github-provided implementation of this behaviour and the
# original repo is unmaintained. Thus the new behaviour is that actions won't trigger
# when using [skip ci]. See
# https://github.blog/changelog/2021-02-08-github-actions-skip-pull-request-and-push-workflows-with-skip-ci/
should-deploy:
runs-on: ubuntu-latest
outputs:
should-run: ${{github.repository_owner == 'UAlbertaALTLab' && github.ref == 'refs/heads/main' }}
steps:
- run: true
should-update-dev:
runs-on: ubuntu-latest
outputs:
should-run: ${{ github.repository_owner == 'UAlbertaALTLab' && github.ref == 'refs/heads/dev' }}
steps:
- run: true
# Run Pytest unit tests
unit-test:
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v4
- name: 🐍 Set up Python ${{ env.ACTIONS_PYTHON_VERSION }}
uses: actions/setup-python@v5
# actions/cache below uses this id to get the exact python version
id: setup-python
with:
python-version: ${{ env.ACTIONS_PYTHON_VERSION }}
- name: 🖥 Install system dependencies
run: sudo apt-get install -y libfoma0
- name: ☤ Install pipenv
run: python3 -m pip install pipenv==2021.11.9
# This started out life as a copy-paste from
# https://github.com/actions/cache/blob/main/examples.md#python---pipenv
- uses: actions/cache@v4
with:
path: ~/.local/share/virtualenvs
key: ${{ runner.os }}-python-${{ steps.setup-python.outputs.python-version }}-pipenv-${{ hashFiles('Pipfile.lock') }}
- name: 📥 Install dependencies
run: |
pipenv install --dev
# Install pytest plugin to show failed tests on the web
pipenv run pip install pytest-github-actions-annotate-failures
- name: Do LFS checkout
# actions/checkout@v2 has a `with: lfs: true` option, but it only
# knows how to talk to GitHub’s LFS server.
#
# These actions are automatic if you have run `git lfs install`
# even once on your dev machine.
run: git lfs install --local && git lfs fetch && git lfs checkout
- name: 🧶 Run linters/static-analysis
run: |
pipenv run mypy src
- name: 🩺 Run unit tests
env:
DEBUG: "True"
run: pipenv run test -v --cov=src --cov-report=xml
- name: Check working directory clean
run: ./libexec/check-git-status
- name: Check that generated files are up-to-date
# A few auto-generated files are checked in for convenience; ensure
# that they are up-to-date.
if: github.ref != 'refs/heads/dev'
run: "pipenv run docker/helper.py make-yaml
&& if ! ./libexec/check-git-status ; then
echo Error: running make-yaml resulted in changed files. When
changing template files, please ensure that updated generated
files get checked in too. 1>&2 ;
exit 1 ;
fi"
- name: 📤 Upload Codecov coverage report
uses: codecov/codecov-action@v4
with:
token: ${{ secrets.CODECOV_TOKEN }}
# Runs Cypress acceptance tests
integration-test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: 🐍 Set up Python ${{ env.ACTIONS_PYTHON_VERSION }}
uses: actions/setup-python@v5
id: setup-python
with:
python-version: ${{ env.ACTIONS_PYTHON_VERSION }}
- name: Setup Node ${{ env.ACTIONS_NODE_VERSION }}
uses: actions/setup-node@v4
with:
node-version: ${{ env.ACTIONS_NODE_VERSION }}
cache: npm
- name: 🖥 Install system dependencies
run: sudo apt-get install -y libfoma0 libgtk2.0-0 libgtk-3-0 libgbm-dev libnotify-dev libgconf-2-4 libnss3 libxss1 libasound2 libxtst6 xauth xvfb
- name: ☤ Install pipenv
run: python3 -m pip install pipenv==2021.11.9
# This started out life as a copy-paste from
# https://github.com/actions/cache/blob/main/examples.md#python---pipenv
- uses: actions/cache@v4
with:
path: ~/.local/share/virtualenvs
key: ${{ runner.os }}-python-${{ steps.setup-python.outputs.python-version }}-pipenv-${{ hashFiles('Pipfile.lock') }}
- name: 📥 Install Python dependencies
run: |
pipenv install --dev
- name: Do LFS checkout
# actions/checkout@v2 has a `with: lfs: true` option, but it only
# knows how to talk to GitHub’s LFS server.
#
# These actions are automatic if you have run `git lfs install`
# even once on your dev machine.
run: git lfs install --local && git lfs fetch && git lfs checkout
- name: 📥 Install Node dependencies
run: npm ci
- name: 🛑 Halt tests if Cypress tests are marked as '.only'
run: npm run stop-only
- name: 🏗 Build frontend
run: npm run build
- name: 🌲 Run Cypress tests
env:
DEBUG: "True"
# NOTE: only set on the upstream repo, i.e., UAlbertaALTLab/morphodict
CYPRESS_RECORD_KEY: "${{ secrets.CYPRESS_RECORD_KEY }}"
run: |
# Enables uploading test runs to Cypress Dashboard:
if [ -n "$CYPRESS_RECORD_KEY" ] ; then export CYPRESS_OPTS="--key $CYPRESS_RECORD_KEY" ; fi
pipenv run ./scripts/run-cypress --no-interactive
- name: Archive cypress videos
uses: actions/upload-artifact@v4
with:
name: cypress-videos
path: |
cypress/videos
build-docker-image-dev:
runs-on: ubuntu-latest
# Only build the Docker Image when we're deploying!
needs:
- should-update-dev
if: needs.should-update-dev.outputs.should-run == 'true'
steps:
- name: Login to GitHub Container Registry
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.repository_owner }}
password: ${{ secrets.GHCR_PERSONAL_ACCESS_TOKEN }}
- uses: actions/checkout@v4
- name: Build and push Docker images
uses: docker/build-push-action@v6
with:
# build-push-action with the default ‘git context’ ignores the
# .dockerignore file
# https://github.com/docker/build-push-action/issues/182
context: .
file: docker/Dockerfile
push: true
# hopefully this will speed up builds and save disk space by
# sharing layers with the existing docker image, where possible
cache-from: |
type=registry,ref=ghcr.io/ualbertaaltlab/itwewina.altlab.app:dev
tags: |
ghcr.io/ualbertaaltlab/itwewina.altlab.app:${{ github.sha }}
update-docker-dev-tag:
runs-on: ubuntu-latest
needs:
- should-update-dev
# - unit-test
# - integration-test
- build-docker-image-dev
if: needs.should-update-dev.outputs.should-run == 'true'
steps:
- name: Login to GitHub Container Registry
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.repository_owner }}
password: ${{ secrets.GHCR_PERSONAL_ACCESS_TOKEN }}
- uses: actions/checkout@v4
- name: 🐍 Set up Python ${{ env.ACTIONS_PYTHON_VERSION }}
uses: actions/setup-python@v5
with:
python-version: ${{ env.ACTIONS_PYTHON_VERSION }}
- name: Install requests
run: pip install requests
- name: Update tag
run: docker/copy-registry-tag ${{ github.sha }} dev
env:
GHCR_PERSONAL_ACCESS_TOKEN: ${{ secrets.GHCR_PERSONAL_ACCESS_TOKEN }}
build-docker-image:
runs-on: ubuntu-latest
# Only build the Docker Image when we're deploying!
needs:
- should-deploy
if: needs.should-deploy.outputs.should-run == 'true'
steps:
- name: Login to GitHub Container Registry
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.repository_owner }}
password: ${{ secrets.GHCR_PERSONAL_ACCESS_TOKEN }}
- uses: actions/checkout@v4
- name: Build and push Docker images
uses: docker/build-push-action@v6
with:
# build-push-action with the default ‘git context’ ignores the
# .dockerignore file
# https://github.com/docker/build-push-action/issues/182
context: .
file: docker/Dockerfile
push: true
# hopefully this will speed up builds and save disk space by
# sharing layers with the existing docker image, where possible
cache-from: |
type=registry,ref=ghcr.io/ualbertaaltlab/itwewina.altlab.app:latest
tags: |
ghcr.io/ualbertaaltlab/itwewina.altlab.app:${{ github.sha }}
trigger-deployment:
runs-on: ubuntu-latest
needs:
- should-deploy
- unit-test
- integration-test
- build-docker-image
if: needs.should-deploy.outputs.should-run == 'true'
steps:
- name: Login to GitHub Container Registry
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.repository_owner }}
password: ${{ secrets.GHCR_PERSONAL_ACCESS_TOKEN }}
- uses: actions/checkout@v4
- name: 🐍 Set up Python ${{ env.ACTIONS_PYTHON_VERSION }}
uses: actions/setup-python@v5
with:
python-version: ${{ env.ACTIONS_PYTHON_VERSION }}
- name: Install requests
run: pip install requests
- name: Update tag
run: docker/copy-registry-tag ${{ github.sha }} latest
env:
GHCR_PERSONAL_ACCESS_TOKEN: ${{ secrets.GHCR_PERSONAL_ACCESS_TOKEN }}
- name: send HTTP request to deploy.altlab.dev webhook
# Be careful with spacing here.
#
# What https://yaml-multiline.info *doesn’t* warn you about: although
# `>-` means “replace newlines with spaces,” if you have an extra
# space on the next line, the newline gets preserved!
#
# So although
#
# foo: >-
# a
# a
#
# means `{ "foo": "a a" }`,
#
# foo: >-
# a
# a
#
# turns into `{ "foo": "a\n a" }` !
# run: >-
# curl -X POST https://deploy.altlab.dev/itwewina --fail
# -d '{ "secret": "${{ secrets.DEPLOY_ALTLAB_DEV_ITWEWINA_KEY }}" }'
# -H 'Content-Type: application/json'
run: echo "This step has been temporarily disabled, call the deploy script."