Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
ansible_lza_install_common
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Digital Preservation
ansible_lza_install_common
Commits
c60274d9
Commit
c60274d9
authored
8 months ago
by
Jörg Sachse
Browse files
Options
Downloads
Patches
Plain Diff
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
8 months ago
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab-ci.yml
+34
-7
34 additions, 7 deletions
.gitlab-ci.yml
with
34 additions
and
7 deletions
.gitlab-ci.yml
+
34
−
7
View file @
c60274d9
...
...
@@ -16,10 +16,12 @@ variables:
ANSIBLE_FORCE_COLOR
:
'
true'
PY_COLORS
:
'
1'
test-job
:
test-job
-debian12
:
stage
:
test
tags
:
-
"
shell"
vars
:
SCENARIO
:
"
virtualbox_debian12"
script
:
# make sure that Ansible Vaults are present and can be decrypted
-
echo "${VAULT_INSTALL_COMMON}" > ../lza_install_common.pass
...
...
@@ -27,14 +29,39 @@ test-job:
-
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
default
-
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 default
-
molecule converge --scenario-name default
-
molecule idempotence --scenario-name default
# - molecule verify --scenario-name default
-
molecule destroy --scenario-name default
-
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}
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}
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment