Skip to content
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

Move docker files to folder and add CI step to publish docker images #367

Merged
merged 2 commits into from
Mar 3, 2022

Conversation

ChristopherHogan
Copy link
Collaborator

Closes #290. Closes #291.

This change enables automatically building docker images and pushing them to dockerhub every time we tag a new release. I've also added a way to force the images to be built and uploaded via the build_docker_images workflow dispatch option.

@ChristopherHogan ChristopherHogan added the testing Related to automated testing or CI label Mar 3, 2022
@coveralls
Copy link

coveralls commented Mar 3, 2022

Coverage Status

Coverage decreased (-0.08%) to 81.559% when pulling 4f6fa4e on chogan/automate_docker into b815c1f on master.

Copy link
Member

@hyoklee hyoklee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about having a separate Action for Docker image publishing since you want to run it only when there's a new tag?
main.yml seems too crowded.

@@ -92,3 +94,38 @@ jobs:
uses: coverallsapp/github-action@master
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
build-docker-images:
if: ${{ github.ref_type == 'tag' || github.event.inputs.build_docker_images }}
runs-on: ubuntu-20.04
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use ubuntu-latest so we don't have to update it when a new Ubuntu release comes out.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I used to have it set to ubuntu-latest but when it updated, it broke our builds. I'd rather have explicit control over updating so that we can do it when its convenient to us rather than having to put out fires. See #50 and #51.

@ChristopherHogan
Copy link
Collaborator Author

How about having a separate Action for Docker image publishing since you want to run it only when there's a new tag?
main.yml seems too crowded.

Done.

@ChristopherHogan ChristopherHogan merged commit b395d17 into master Mar 3, 2022
@ChristopherHogan ChristopherHogan deleted the chogan/automate_docker branch March 3, 2022 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Related to automated testing or CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move the Dockerfiles to a subfolder Make the Docker image creation a GitHub action
3 participants