Github workflow to build container images #16
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.
While it's a good idea to build containers manually, it adds additional overhead to anyone who is maintaining the exporter in a container environment. GitHub has actions and Container Registry, so maintaining a prebuilt container is no longer an overhead.
This workflow builds the container and uploads to GHCR when ever a new release is made and when a push to main or dev happens. Latter ones are useful for development flows, while the release flows will push a latest tag in addition to the release tag versions, which allows easy access to old versions as well as current versions.