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
Kubernetes/Cluster deployment #105
Comments
For docker, see also: https://simonwillison.net/2018/Nov/19/smaller-python-docker-images/ |
https://docs.docker.com/docker-hub/builds/ |
We would love to have a docker build and publish at the end of our CI pipeline. Currently, we are building (not publishing) a docker image as a step of the I think using the automated building from docker hub means the docker image will be built independently from the CI fail/success status, right? |
Yes, I also think so the docker hub build will be independent of CI fail/success status. Not quite sure about it but might we need to update the docker hub after every new build?. @sk1p and @uellue I am moving forward with this https://docs.docker.com/docker-hub/builds/ and hope everything would be fine at the end. |
Hmm, I'm not convinced that's the way to go. How do you prevent broken docker images from being pushed? If your answer is using autotest, how do you prevent having a completely separate test run from the rest of our pipeline? Feel free to play around with the build service, but you'll have to convince me to make it the official image 😁 On our road map, we have a migration to azure pipelines for CI, to consolidate our travis and appveyor builds into a single service. We already have the basics implemented in #565, it's mostly missing replacements for some travis specifics (basically |
See also #67 for auth related questions.
Edit: Removed HDFS aspects
The text was updated successfully, but these errors were encountered: