ci: build docker image and push to container registry #52
Conversation
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.
This pull request introduces a new workflow for building and optionally pushing Docker images. The changes include the creation of two new workflow files: one for triggering the Docker build process and another reusable workflow for the actual build and push operations.
New Workflows for Docker Build and Push
.github/workflows/build-docker-images.yml: This workflow is designed to trigger Docker builds on specific branches (main,dev,demo) and during specific pull request events (opened,ready_for_review,reopened,synchronize). It uses a matrix strategy to handle different applications (backend,webapp) and their respective Dockerfiles..github/workflows/build-docker.yml: This reusable workflow handles the actual Docker build and push process. It includes steps for checking out the code, logging into Docker, setting up Docker Buildx, determining the tag name based on the branch, and building and optionally pushing the Docker image.