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

Setup docker github workflows #36

Open
mjpitz opened this issue Jul 5, 2020 · 2 comments
Open

Setup docker github workflows #36

mjpitz opened this issue Jul 5, 2020 · 2 comments
Labels
effort: 2 type: chore Other necessary (but less impactful) tasks. work: obvious The situation is obvious, best practices used.
Projects

Comments

@mjpitz
Copy link
Member

mjpitz commented Jul 5, 2020

We should have workflows to build and push the docker images.

On branches, docker images should be built. Since these are largely SDK containers, there isn't much to test about them. When the branch is main, we should push a :latest tag to dockerhub.

@mjpitz mjpitz added this to To do in deps.cloud via automation Jul 5, 2020
@mjpitz mjpitz added effort: 2 type: chore Other necessary (but less impactful) tasks. work: obvious The situation is obvious, best practices used. labels Jul 5, 2020
@abitrolly
Copy link

@mjpitz
Copy link
Member Author

mjpitz commented Mar 9, 2021

Different project. This is specifically for the API which has its own set of images used to generate the associated code rather than requiring callers to have the proper protoc environment configured. I could probably move some of this over to using my bin-vendor project, but I think the python install requires libraries and one benefit to the container is that those are encapsulated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: 2 type: chore Other necessary (but less impactful) tasks. work: obvious The situation is obvious, best practices used.
Projects
deps.cloud
  
To Do
Development

No branches or pull requests

2 participants