New buildbot ignores sub-module branches #88432
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
5 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-buildbot#88432
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?
Some branches (including one used in the Spright Fright production) require a certain add-ons branch to be used. So far the way to do this was by setting a submodule branch in Blender's
make update
. E.g. like here {https://developer.blender.org/diffusion/B/browse/asset-browser-poselib/build_files/utils/make_update.py$177-183}:The new buildbot doesn't checkout the branch as specified anymore, meaning the builds might not be usable for testing.
In the Blender Studio, animators use this to work with the
asset-browser-poselib
branch, which is developed in partnership with Spright Fright production.Added subscriber: @JulianEisel
I actually fixed an issue regarding how it this was done as it was not working correctly.
I will add a config to override the default being master.
I will run test on your this specific branch.
You can check in the logs in the
update-code
step too verify that it was done correctly.Do you want this branch to be nightly also ?
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @ZedDB
Thanks @ponderz! I can't spend time on this right now unfortunately, but will keep an eye on things.
That would be great! (Not sure if the builds are triggered manually currently. I think @ZedDB handles that.)
I guess these could be updated nightly, yes.
This way the artists at the studio don't have to manually trigger builds (that can take a long time to finish for windows)
For branch this output is expected.
Can be reviewed in the
update-code
stepAdded subscriber: @brecht
Can't we just use the
make_update.py
from the Blender repo, that auto-detects branches?There are some cases where it makes sense to move code into the buildbot repo, but this one doesn't make sense to me.
Can't do that.
That script did not work in certain circumstances.
We could eventually merge it back in once we proper configurations that can drive it.
I do need to explain a bit more though.
But that's lengthy discussion.
Changed status from 'Confirmed' to: 'Resolved'
The approach has been reworked as discussed with @brecht
Will update Wiki with details during deployment today.
Wiki updated with summary of changes.