Update github actions - #193
Merged
Merged
Conversation
use https://github.com/docker/github-builder instead of assembling a pipeline by hand. Contaienrs are now built on every Pull Request for easier testing and on every tag push.
This file contains hidden or 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
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.
Change the github actions ci to use the new docker recommended builder (https://github.com/docker/github-builder). This is easier to maintain and automatically uses all the new features and build improvements (build matrix for amd64 / arm64 for example).
This results in the following changes for the container build / release process:
Containers are now built when a new version tag is pushed. These containers automaticly get pushed to ghcr.io with a tag corresponding to their version, and the latest container will automaticly get the latest tag.
The
releasesbranch is superseded with this change.Containers are also automatically built for Pull requests, making it easier to see if the changes even build and to test the changes. These containers don't get pushed to ghcr.io.
Resolves #191