-
Notifications
You must be signed in to change notification settings - Fork 60
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
Leaner release process #47
Comments
Thanks @oliverpool, this is very helpful! Curios if you might be interested in taking a stab at contributing support for some of these things? attaching some feedback/questions below
This is great, that way we can also ensure that we only build and push one image (and not every single image in the list)
Are you unable to see the public Drone CI connected to the repo? Github Actions are great, however our organizational recommendation is to use Drone so this repository has been following that
Makes sense to me!
I do think it'll probably still make sense to keep a couple of Ubuntu versions available for convenience
Makes sense to me
👍 |
Thank you for the feedback (and sorry for my late reply). I unfortunately don't have time (and competences) to port this to drone (however as you point out, I can see all build logs). Feel free to copy any code from my repo (I explicitly used the same license). |
Hi, after making a couple of PRs (#34 #39 #43) I thought that the process for releasing new images could be simplified.
I ended up creating a new repo for CPU images: https://github.com/oliverpool/blender-cpu-image/pkgs/container/blender-cpu-image
Main differences:
ghcr.io/oliverpool/blender-cpu-image:3.3.0
I also simplified the Dockerfile:
/bin/python
to ease its use)Feel free to have a look. I would really like to have some feedback!
The text was updated successfully, but these errors were encountered: