Project Tools: Can't fetch the current release of Blender #301

Closed
opened 2024-05-27 22:48:35 +02:00 by Nick Alberelli · 3 comments
Member

I am testing out the studio tools, and I am having an issue when changing the value of the blender branch. With the current update blender script users are limited to only the version of blenders with daily builds.

Current that is:

v33 == 3.3.x
v36 == 3.6.x
main == v4.2.x

# Source: https://builder.blender.org/download/daily/?format=json&v=1

I thought that v41 for Blender 4.1.x would be avaliable but it is not. I expect many users/productions will want to be using whatever is avaliable here: https://www.blender.org/download/ or on the latest stable LTS release. This issue has come up as I was trying to setup a new project but needed to use a previous stable build of blender because of this issue

I am testing out the studio tools, and I am having an issue when changing the value of the blender branch. With the current update blender script users are limited to only the version of blenders with daily builds. Current that is: ``` v33 == 3.3.x v36 == 3.6.x main == v4.2.x # Source: https://builder.blender.org/download/daily/?format=json&v=1 ``` I thought that `v41` for Blender 4.1.x would be avaliable but it is not. I expect many users/productions will want to be using whatever is avaliable here: https://www.blender.org/download/ or on the latest stable LTS release. This issue has come up as I was trying to setup a new project but needed to use a previous stable build of blender because of [this issue](https://projects.blender.org/blender/blender/issues/122339)
Nick Alberelli added the
Kind
Breaking
Kind
Studio Request
Kind
Enhancement
labels 2024-05-27 22:48:36 +02:00
Author
Member

@ZedDB this was one thing I want to chat with u about before I head out BTW!

@ZedDB this was one thing I want to chat with u about before I head out BTW!

The intention of the "update_blender" script was to allow people to update LTS or pre-release versions easily during production.

As the studio is not using any builds outside of the buildbot builds, this is not part of the script.
Sadly the download method would be quite a bit different for builds from https://www.blender.org/download/ than from the build bot as our regular download doesn't have a json backend. So we would have to set up a specific web crawler for this.

For users that are not using the bleeding edge or LTS releases, I would just manually setup the artifacts folder as it shouldn't have to be touched after the initial setup of the project (as they are not moving from that version).

The intention of the "update_blender" script was to allow people to update LTS or pre-release versions easily during production. As the studio is not using any builds outside of the buildbot builds, this is not part of the script. Sadly the download method would be quite a bit different for builds from https://www.blender.org/download/ than from the build bot as our regular download doesn't have a json backend. So we would have to set up a specific web crawler for this. For users that are not using the bleeding edge or LTS releases, I would just manually setup the artifacts folder as it shouldn't have to be touched after the initial setup of the project (as they are not moving from that version).
Author
Member
Resolved by: https://projects.blender.org/studio/blender-studio-pipeline/commit/e715ee2cc680ca83ebdbc911ae29d4619d826ea8 Results are avaliable: https://studio.blender.org/pipeline/td-guide/blender_setup#manually-deploying-blender-versions-of-your-choosing
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/blender-studio-tools#301
No description provided.