Skip to content
Snippets Groups Projects
Commit c60274d9 authored by Jörg Sachse's avatar Jörg Sachse
Browse files

test: add CI routine for testing AlmaLinux 8

parent 730b6014
No related branches found
No related tags found
No related merge requests found
Pipeline #7113 failed
...@@ -16,10 +16,12 @@ variables: ...@@ -16,10 +16,12 @@ variables:
ANSIBLE_FORCE_COLOR: 'true' ANSIBLE_FORCE_COLOR: 'true'
PY_COLORS: '1' PY_COLORS: '1'
test-job: test-job-debian12:
stage: test stage: test
tags: tags:
- "shell" - "shell"
vars:
SCENARIO: "virtualbox_debian12"
script: script:
# make sure that Ansible Vaults are present and can be decrypted # make sure that Ansible Vaults are present and can be decrypted
- echo "${VAULT_INSTALL_COMMON}" > ../lza_install_common.pass - echo "${VAULT_INSTALL_COMMON}" > ../lza_install_common.pass
...@@ -27,14 +29,39 @@ test-job: ...@@ -27,14 +29,39 @@ test-job:
- rm -rf ../ansible_vaults/ - rm -rf ../ansible_vaults/
- git clone https://gitlab+deploy-token-25:${VAULT_ACCESS_TOKEN}@git.slub-dresden.de/slub-referat-2-3/ansible_vaults.git ../ansible_vaults/; \ - git clone https://gitlab+deploy-token-25:${VAULT_ACCESS_TOKEN}@git.slub-dresden.de/slub-referat-2-3/ansible_vaults.git ../ansible_vaults/; \
# run Molecule tests # run Molecule tests
- molecule syntax --scenario-name default - molecule syntax --scenario-name ${SCENARIO}
# We cannot use `molecule lint` anymore because: # We cannot use `molecule lint` anymore because:
# - https://github.com/ansible-community/molecule/pull/3802 "Remove lint command" # - https://github.com/ansible-community/molecule/pull/3802 "Remove lint command"
# - https://github.com/ansible-community/molecule/discussions/3825#discussioncomment-4908366 # - https://github.com/ansible-community/molecule/discussions/3825#discussioncomment-4908366
- yamllint --strict --format colored ./ - yamllint --strict --format colored ./
- ansible-lint --format full --profile production --strict --force-color ./ - ansible-lint --format full --profile production --strict --force-color ./
- molecule create --scenario-name default - molecule create --scenario-name ${SCENARIO}
- molecule converge --scenario-name default - molecule converge --scenario-name ${SCENARIO}
- molecule idempotence --scenario-name default - molecule idempotence --scenario-name ${SCENARIO}
# - molecule verify --scenario-name default # - molecule verify --scenario-name ${SCENARIO}
- molecule destroy --scenario-name default - molecule destroy --scenario-name ${SCENARIO}
test-job-alma8:
stage: test
tags:
- "shell"
vars:
SCENARIO: "virtualbox_alma8"
script:
# make sure that Ansible Vaults are present and can be decrypted
- echo "${VAULT_INSTALL_COMMON}" > ../lza_install_common.pass
- export ANSIBLE_VAULT_PASSWORD_FILE=../lza_install_common.pass
- rm -rf ../ansible_vaults/
- git clone https://gitlab+deploy-token-25:${VAULT_ACCESS_TOKEN}@git.slub-dresden.de/slub-referat-2-3/ansible_vaults.git ../ansible_vaults/; \
# run Molecule tests
- molecule syntax --scenario-name ${SCENARIO}
# We cannot use `molecule lint` anymore because:
# - https://github.com/ansible-community/molecule/pull/3802 "Remove lint command"
# - https://github.com/ansible-community/molecule/discussions/3825#discussioncomment-4908366
- yamllint --strict --format colored ./
- ansible-lint --format full --profile production --strict --force-color ./
- molecule create --scenario-name ${SCENARIO}
- molecule converge --scenario-name ${SCENARIO}
- molecule idempotence --scenario-name ${SCENARIO}
# - molecule verify --scenario-name ${SCENARIO}
- molecule destroy --scenario-name ${SCENARIO}
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment