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

Leaner release process #47

Open
oliverpool opened this issue Sep 12, 2022 · 2 comments
Open

Leaner release process #47

oliverpool opened this issue Sep 12, 2022 · 2 comments
Labels
enhancement 🏋️ New feature or request

Comments

@oliverpool
Copy link
Contributor

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:

  • the release process is much easier: I just have to push a tag (corresponding to a blender version)
  • the build happens via github actions so anyone can see the log
  • the docker image is stored on github infrastructure ghcr.io/oliverpool/blender-cpu-image:3.3.0
  • the tag contains the patch version (3.3.0 and not 3.3)
  • the base image is (currently) ubuntu 22.04
  • it is limited to CPU rendering

I also simplified the Dockerfile:

  • python is shipped with blender, so no need for a separate install (I just add a symlink to /bin/python to ease its use)
  • numpy is a recent version (so no reinstalling)

Feel free to have a look. I would really like to have some feedback!

@juniorxsound
Copy link
Contributor

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

the release process is much easier: I just have to push a tag (corresponding to a blender version)

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)


the build happens via github actions so anyone can see the log

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


the tag contains the patch version (3.3.0 and not 3.3)

Makes sense to me!


the base image is (currently) ubuntu 22.04

I do think it'll probably still make sense to keep a couple of Ubuntu versions available for convenience


python is shipped with blender, so no need for a separate install (I just add a symlink to /bin/python to ease its use)

Makes sense to me


numpy is a recent version (so no reinstalling)

👍

@oliverpool
Copy link
Contributor Author

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 🏋️ New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants