Add Docker Hub release workflow #31
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
dehume
approved these changes
Aug 29, 2023
|
Put up a PR to expose the secret here: https://github.com/MaterializeInc/i2/pull/1121 |
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.
Adding a Docker image build workflow to build a new image whenever there is a new release. That way we would conveniently have a Metabase docker image with the Materialize driver available on Docker Hub for testing purposes.
Closes #30
@benesch, no need to review this, but if you could just add a
DOCKER_HUB_MATERIALIZEBOT_API_KEYsecret to this repo similar to what we've done with datagen that would be great!