Add Archivematica upgrade test workflow #154
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
replaceafill
force-pushed
the
dev/test-am-upgrade
branch
from
57b5cac to
86215b4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Similarly to #146 and #148 this adds a very basic GitHub workflow to test Archivematica upgrades.
It's implemented with a Podman container orchestrated with podman-compose and it reuses the requirements and variables included in the
archivematica-jammyplaybook.The workflow can be triggered manually from the Actions tab.
For now it only shows the
X-Archivematica-Versionheader set by the Dashboard API before and after the upgrade and calls a couple of API endpoints, but we can extend it in the future with more assertive steps that guarantee behavior is maintained across versions (e.g. running transfers, downloading AIPs, searching, etc).