@@ -200,3 +200,110 @@ jobs:
200
200
- name : Setup tmate debug session
201
201
uses : mxschmitt/action-tmate@v3
202
202
if : env.RUN_TMATE
203
+ <<<<<<< HEAD
204
+ =======
205
+ test :
206
+ name : >-
207
+ test (${{ matrix.scenario }}) -
208
+ ${{ matrix.platform }}-${{ matrix.architecture }}
209
+ needs :
210
+ - diagnostics
211
+ permissions :
212
+ # actions/checkout needs this to fetch code
213
+ contents : read
214
+ # This line is long, but if I use a block style indicator then GH
215
+ # Actions doesn't parse and execute the expression.
216
+ # yamllint disable-line rule:line-length
217
+ runs-on : ubuntu-${{ startsWith(matrix.architecture, 'arm') && '24.04-arm' || 'latest' }}
218
+ strategy :
219
+ fail-fast : false
220
+ matrix :
221
+ architecture :
222
+ - amd64
223
+ - arm64
224
+ platform :
225
+ - amazonlinux2023-systemd
226
+ - debian10-systemd
227
+ - debian11-systemd
228
+ - debian12-systemd
229
+ - debian13-systemd
230
+ - fedora41-systemd
231
+ - fedora42-systemd
232
+ - kali-systemd
233
+ - ubuntu-22-systemd
234
+ - ubuntu-24-systemd
235
+ scenario :
236
+ - default
237
+ steps :
238
+ - name : Apply standard cisagov job preamble
239
+ uses : cisagov/action-job-preamble@v1
240
+ with :
241
+ # This functionality is poorly implemented and has been
242
+ # causing problems due to the MITM implementation hogging or
243
+ # leaking memory. As a result we disable it by default. If
244
+ # you want to temporarily enable it, simply set
245
+ # monitor_permissions equal to "true".
246
+ #
247
+ # TODO: Re-enable this functionality when practical. See
248
+ # cisagov/skeleton-ansible-role#227 for more details.
249
+ monitor_permissions : " false"
250
+ # Use a variable to specify the permissions monitoring
251
+ # configuration. By default this will yield the
252
+ # configuration stored in the cisagov organization-level
253
+ # variable, but if you want to use a different configuration
254
+ # then simply:
255
+ # 1. Create a repository-level variable with the name
256
+ # ACTIONS_PERMISSIONS_CONFIG.
257
+ # 2. Set this new variable's value to the configuration you
258
+ # want to use for this repository.
259
+ #
260
+ # Note in particular that changing the permissions
261
+ # monitoring configuration *does not* require you to modify
262
+ # this workflow.
263
+ permissions_monitoring_config : ${{ vars.ACTIONS_PERMISSIONS_CONFIG }}
264
+ - id : setup-env
265
+ uses : cisagov/setup-env-github-action@develop
266
+ - uses : actions/checkout@v4
267
+ - id : setup-python
268
+ uses : actions/setup-python@v5
269
+ with :
270
+ python-version : ${{ steps.setup-env.outputs.python-version }}
271
+ - uses : actions/cache@v4
272
+ env :
273
+ BASE_CACHE_KEY : ${{ github.job }}-${{ runner.os }}-\
274
+ py${{ steps.setup-python.outputs.python-version }}-
275
+ with :
276
+ path : ${{ env.PIP_CACHE_DIR }}
277
+ key : ${{ env.BASE_CACHE_KEY }}\
278
+ ${{ hashFiles('**/requirements-test.txt') }}-\
279
+ ${{ hashFiles('**/requirements.txt') }}
280
+ restore-keys : |
281
+ ${{ env.BASE_CACHE_KEY }}
282
+ - name : Install dependencies
283
+ run : |
284
+ python -m pip install --upgrade pip
285
+ pip install --upgrade --requirement requirements-test.txt
286
+ - name : Set up Docker Buildx
287
+ uses : docker/setup-buildx-action@v3
288
+ # AppArmor interferes when running Molecule tests against Fedora
289
+ # 40 and 41; it does not allow the privileged container to run
290
+ # sudo and hence Ansible is unable to do anything. See
291
+ # fedora-cloud/docker-brew-fedora#117 for more details.
292
+ #
293
+ # There is a growing consensus that AppArmor causes too many
294
+ # problems and should not be active on the short-lived GitHub
295
+ # runners. See, for example,
296
+ # actions/runner-images/issues/10015. To avoid problems in the
297
+ # future, it makes sense to simply disable AppArmor altogether
298
+ # before running Molecule tests.
299
+ - name : Disable AppArmor
300
+ uses : cisagov/action-disable-apparmor@v1
301
+ - name : Run molecule tests
302
+ run : >-
303
+ molecule test
304
+ --platform-name ${{ matrix.platform }}-${{ matrix.architecture }}
305
+ --scenario-name ${{ matrix.scenario }}
306
+ - name : Setup tmate debug session
307
+ uses : mxschmitt/action-tmate@v3
308
+ if : env.RUN_TMATE
309
+ >>>>>>> 54e395efa2409780c0574d266fe68bce1c9b7060
0 commit comments