Project Tools: Can't fetch the current release of Blender #301
Labels
No Label
Kind
Breaking
Kind
Bug
Kind: Community
Kind
Documentation
Kind
Easy
Kind
Enhancement
Kind
Feature
Kind
Proposal
Kind
Security
Kind
Studio Request
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/blender-studio-tools#301
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
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@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).
Resolved by:
e715ee2cc6
Results are avaliable: https://studio.blender.org/pipeline/td-guide/blender_setup#manually-deploying-blender-versions-of-your-choosing