Updated docker build workflow for manual trigger and tag event#104
Merged
andrewdavidsmith merged 4 commits intomasterfrom Aug 14, 2023
Merged
Updated docker build workflow for manual trigger and tag event#104andrewdavidsmith merged 4 commits intomasterfrom
andrewdavidsmith merged 4 commits intomasterfrom
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
2 participants
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.
I update the workflow for docker build. I added some user instructions in
README.mdand maintainer instructions inMAINTAINERS.md.Updated the workflow.
This workflow is for building and possibly pushing the docker image for
a commit tagged by a version number. It is triggered either manually or by
a tag event of type
v*.*.*, which is intended for new releases. Currently,pushing to ghcr.io can happen only to commits tagged by a version number. This
is intended to associate every docker image with a version number. This means
that there is no option to push the image for the latest commit, even though
we can build the image for testing purposes.
Manual trigger
In Actions, go to
Docker image buildand click"Run workflow" and choose from the following options.
Options:
- 'Build latest commit': for testing for the latest commit
- 'Build existing version': for testing a particular version
- 'Build + push existing version': for publishing a particular version
Tag event
In a tag event of type "v*..", such as new release or retagging, this work
flow is triggered to build and publish the image for the tagged version
number.
Usage
The image can be pulled by one of the following commands.
docker pull ghcr.io/smithlabcode/dnmtools:latestdocker pull ghcr.io/smithlabcode/dnmtools:<7-DIGIT SHA>docker pull ghcr.io/smithlabcode/dnmtools:v<VERSION NUMBER> (e.g. v1.3.0)