-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Push docker images directly from CI #120
Comments
For tagged release it would also make sense to publish in the official docker library at https://github.com/docker-library/official-images We haven't done that so far because 0.x Having a crystal in the official library will give us Eventually, keeping only the ci images for ourselves should be enough regarding crytallang/crystal docker images. |
I think we just have to activate the It probably makes sense to roll that out after crystal-lang/crystal#11273 The only dodgy part is overriding the That being said, it's not hard to fix if it goes wrong. With goes wrong I mean either forgetting to update The same issue with |
|
This has been resolved by crystal-lang/crystal#11309 and #156 Versioned Docker images are now published automatically from the CI workflow. Tagging of the latest release happens manually via the shell script helper. |
Right now nightlies images are being pushed already, the difference lies in that the images of releases (apparently) uses OBS packages instead of hard-coded binaries. The intention as we understand it is to be able to deliver updateable images. However, that doesn't seem to be super important: those willing to have such images should simply add the steps to install crystal from a base image.
The text was updated successfully, but these errors were encountered: