Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
ansible_lza_ingest
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_ingest
Commits
7138d45f
Commit
7138d45f
authored
1 year ago
by
Jörg Sachse
Browse files
Options
Downloads
Patches
Plain Diff
test: update Gitlab-CI config to use absolute paths for Ansible Vault password files
parent
c0ad22b6
Branches
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#6072
failed
1 year ago
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab-ci.yml
+16
-8
16 additions, 8 deletions
.gitlab-ci.yml
with
16 additions
and
8 deletions
.gitlab-ci.yml
+
16
−
8
View file @
7138d45f
...
@@ -12,6 +12,15 @@ default:
...
@@ -12,6 +12,15 @@ default:
-
source /opt/molecule/bin/activate
-
source /opt/molecule/bin/activate
-
ansible --version
-
ansible --version
-
molecule --version
-
molecule --version
after_script
:
-
source /opt/molecule/bin/activate
-
molecule destroy --scenario-name ${SCENARIO}
variables
:
SCENARIO
:
"
default"
ANSIBLE_VAULT_PASSWORD_FILE
:
"
${CI_PROJECT_DIR}/molecule/${SCENARIO}/../../../lza_ingest.pass"
ANSIBLE_FORCE_COLOR
:
'
true'
PY_COLORS
:
'
1'
test-job
:
test-job
:
stage
:
test
stage
:
test
...
@@ -19,19 +28,18 @@ test-job:
...
@@ -19,19 +28,18 @@ test-job:
-
"
shell"
-
"
shell"
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_INGEST}" >
../../../lza_ingest.pass
-
echo "${VAULT_INGEST}" >
${ANSIBLE_VAULT_PASSWORD_FILE}
-
export ANSIBLE_VAULT_PASSWORD_FILE=
../../../lza_ingest.pass
-
export ANSIBLE_VAULT_PASSWORD_FILE=
"${ANSIBLE_VAULT_PASSWORD_FILE}"
-
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
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