-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add auto container release action #200
base: master
Are you sure you want to change the base?
Conversation
Now whenever a new tag of SPRAS is pushed to github, the corresponding container from that tag is build and pushed to Dockerhub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to decide on the tagging convention. Then we can merge and test it by making a release.
- name: Log in to Docker Hub | ||
uses: docker/login-action@v1 | ||
with: | ||
username: ${{ vars.DOCKER_USERNAME }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# run release on any version tag vX.Y.Z, e.g. v0.2.1 | ||
- v[0-9]+\.[0-9]+\.[0-9]+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our tags so far have not had a leading v. Should we keep that convention and change the pattern here?
@@ -0,0 +1,43 @@ | |||
name: Release SPRAS on new tags | |||
# This action runs whenever a new tag matching vX.Y.Z is pushed to the repo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adjust depending on what we decide below regarding tag pattern
Now whenever a new tag of SPRAS is pushed to github, the corresponding container from that tag is build and pushed to Dockerhub.