Without a workflow the scenario only runs when somebody remembers to run it locally, which is exactly the situation the tests were written to end. The repository is checked out into a directory named after the role and not after the repository, because the scenario includes the role by its name and molecule puts the parent of the project directory on the roles path. Co-authored-by: Copilot <copilot@github.com>
30 lines
721 B
YAML
30 lines
721 B
YAML
name: Molecule
|
|
|
|
on:
|
|
pull_request:
|
|
types: [ "opened", "reopened", "synchronize" ]
|
|
push:
|
|
branches: [ '**' ]
|
|
tags-ignore: [ '**' ]
|
|
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
molecule:
|
|
name: Molecule
|
|
runs-on: ubuntu-latest-amd64
|
|
steps:
|
|
# The scenario includes the role by its directory name, whose parent is used as roles path.
|
|
- uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
|
|
with:
|
|
path: unix-users
|
|
- name: Install molecule
|
|
run: |
|
|
apt update --yes
|
|
apt install --yes python3-pip
|
|
pip3 install --break-system-packages molecule docker
|
|
- name: Run molecule
|
|
run: molecule test
|
|
working-directory: unix-users
|