Add Custom Docker Build Push GitHub Workflow #62
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
What: Adds a workflow for building custom Docker images of branches and pushing them to the container registry of your choice. Why: This enables easy, reproducible builds of Docker images and should help make it easier to customize Community Edition instances, test pull requests/development branches, and provide Docker images of long running branches (large alpha/beta features) for community testing. Notes: * This allows Docker images with a custom tag/name to be created on demand for any branch containing this workflow and pushed to the specified Docker repository. Two versions of the Docker image will always be pushed, one ending with -latest and one ending with the workflow run number, e.g. my-custom-image-name-latest and my-custom-image-name-42. * The default tag/name of the images is the branch name. * The details required for the workflow to run can either be provided by predefined repository secrets/variables or specified manually when invoking the workflow, the rest are baked into the workflow and should be good most of the time, but can be overridden when invoking the workflow, if needed. * More information on this workflow can be found at either https://docs.hubsfoundation.org/github-workflows.html or https://github.com/Hubs-Foundation/hubs-docs/blob/master/docs/dev-github-workflows.md
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What?
Adds a workflow for building custom Docker images of branches and pushing them to the container registry of your choice.
Why?
This enables easy, reproducible builds of Docker images and should help make it easier to customize Community Edition instances, test pull requests/development branches, and provide Docker images of long running branches (large alpha/beta features) for community testing.
Examples
How to test
Actions > custom-docker-build-pushin your fork.Run workflowbutton.Run workflowbutton at the bottom of the panel you just filled out with details.git reset --hard HEAD~1on your default branch and force push).Documentation of functionality
This is already present at https://github.com/Hubs-Foundation/hubs-docs/blob/master/docs/dev-github-workflows.md / https://docs.hubsfoundation.org/github-workflows.html
Limitations
Not all the utilities that are incorporated in this workflow are necessarily at their latest version (e.g. actions/checkout). This is done in order to keep it in sync with the rest of the implementations of the workflow in the other repositories.
Alternatives considered
None.
Open questions
None.
Additional details or related context
Part of [Hubs-Foundation/.github] Add Custom Docker Build Push action to all Community Edition service repositories (Issue #7)