Enable pre-release
tag for published images
#117
Merged
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.
Release tagging
This PR adapts the release workflow so that the docker containers will be tagged with
latest
orpre-release
depending on if the release is tagged as such. It also adds astable
tag to any non-pre-release that is released from the main branch. This is because it's possible to makelatest
releases from any branch.You can see the pre-release from this branch here: https://github.com/ImperialCollegeLondon/gridlington-vis/releases/tag/v0.3.3-beta
And you can see the
pre-release
tag has bee successfully applied to v0.3.3-beta here https://github.com/ImperialCollegeLondon/gridlington-vis/pkgs/container/gridlington-visIt also ensures the release workflow only runs once instead of 3 times as it was doing before.
Helper scripts
There are two new helper scripts to run the system and one changed one:
run_stable.sh
- changed to get the image tagged asstable
run_pre_release.sh
- gets the image tagged aspre-release
run_version.sh
- gets the image tagged with the version specified. Example usage:bash run_version.sh v0.3.2