Release process bug: absolute path in blender-2.91.2.sha256 #85004
Labels
No Label
legacy module
Development Management
legacy module
Platforms, Builds, Tests & Devices
legacy module
Python API
legacy module
Rendering & Cycles
legacy project
3.3
legacy project
Development Management
legacy project
Documentation
legacy project
Infrastructure: Blender Buildbot
legacy project
Infrastructure: Websites
legacy project
Platform: macOS
legacy project
Platforms, Builds, Tests & Devices
legacy project
Platform: Windows
legacy project
Python API
legacy project
Render & Cycles
Priority::Low
Priority::Normal
Priority::Unbreak Now!
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Information from Developers
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Report
Type::To Do
No Milestone
No project
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-buildbot#85004
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Hello folks,
Not sure if this bugtracker supports blender infrastructure bugs, but I found that the lack of automation of the release process makes such errors possible:
vs
That makes hard to rely on the interface in my CI scripts for BlendNet addon, so could it be somehow fixed? I think relative path works just fine for sha256/md5 files.
And it will be really great if the process could be automated - because manual release process always a potential huge concern from human error and security perspective.
Thank you
Added subscriber: @Rabit
Added subscriber: @EAW
Changed status from 'Needs Triage' to: 'Confirmed'
Confirmed by checking files located at:
https://download.blender.org/release/Blender2.91/
Added subscribers: @Jeroen-Bakker, @ponderz
@ponderz is this something for you? Or @Jeroen-Bakker?
This was fixed few days after this issue was posted
Changed status from 'Confirmed' to: 'Resolved'