studio/blender-studio-pipeline
13
29
Fork 18
Code Issues 17 Pull Requests 4 Projects Releases 1 Activity

Propsal: Move Asset Pipeline into Blender Kitsu #92

New Issue
Closed
opened 2023-06-21 17:58:12 +02:00 by Nick Alberelli · 1 comment
Nick Alberelli commented 2023-06-21 17:58:12 +02:00
Member
Copy Link

Issue

  • Asset Pipeline saves it's task layers in it's own config file that is not read or used by shot builder or any other part of the pipeline
  • Blender Kitsu>Shot Builder is unaware of any casting information from Ktisu, and requires manual input of asset data Source

Solution

Move Asset Pipeline into Blender Kitsu

Addresses some issues in https://studio.blender.org/pipeline/archive/pipeline-proposal-2019/introduction#too-much-manual-work

Make Blender Kitsu Addon the single source of truth for Asset Files, store information about asset files to be imported by shot builder in either JSON file or on Kitsu Server TBD

Asset Pipeline will provide store with information on Collection Names to be imported by Blender Kitsu>Shot Builder

Blender Kitsu>Shot Builder will be able to build the entire production's blend files via Kitsu Data (with empty collections) , including asset files

Steps to Success

  1. Move Asset Pipeline into Blender Kitsu and reuse Convention Checking logic to enforce asset pipeline task types (consider moving these task types into kitsu as well) (addresses some issues in #20)
  2. Report Collection Names from Asset Pipeline to Blender Kitsu
  3. Re-Write Shot Builder to use Collection Names from Kitsu data instead of manual input (Opportunity to address #63 (comment))
# Issue - Asset Pipeline saves it's task layers in it's own config file that is not read or used by shot builder or any other part of the pipeline - `Blender Kitsu>Shot Builder` is unaware of any casting information from Ktisu, and requires manual input of asset data [Source](https://projects.blender.org/studio/blender-studio-pipeline/src/branch/main/scripts-blender/addons/blender_kitsu/shot_builder/docs#api) # Solution ### Move Asset Pipeline into Blender Kitsu Addresses some issues in https://studio.blender.org/pipeline/archive/pipeline-proposal-2019/introduction#too-much-manual-work Make Blender Kitsu Addon the single source of truth for Asset Files, store information about asset files to be imported by shot builder in either JSON file or on Kitsu Server TBD Asset Pipeline will provide store with information on Collection Names to be imported by Blender Kitsu>Shot Builder Blender Kitsu>Shot Builder will be able to build the entire production's blend files via Kitsu Data (with empty collections) , including asset files # Steps to Success 1. Move Asset Pipeline into Blender Kitsu and reuse Convention Checking logic to enforce asset pipeline task types (consider moving these task types into kitsu as well) (addresses some issues in #20) 2. Report Collection Names from Asset Pipeline to Blender Kitsu 3. Re-Write Shot Builder to use Collection Names from Kitsu data instead of manual input (Opportunity to address #63 (comment))
Nick Alberelli added the
Kind
Proposal
 label 2023-06-21 17:58:58 +02:00
Nick Alberelli commented 2023-07-12 18:13:25 +02:00
Author
Member
Copy Link

@fsiddi @SimonThommes @Mets

Per our discussion we are going to plan a new asset pipeline design, that will likely make this irrelevant, so I will be closing this issue for now

@fsiddi @SimonThommes @Mets Per our discussion we are going to plan a new asset pipeline design, that will likely make this irrelevant, so I will be closing this issue for now
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Kind
Breaking
Breaking change that won't be backward compatible

  
Kind
Bug
Something is not working

  
Kind: Community

Issues opened by members of the community / outside the studio

  
Kind
Documentation
Documentation changes

  
Kind
Easy
Simple to complete

  
Kind
Enhancement
Improve existing functionality

  
Kind
Feature
New functionality

  
Kind
Proposal
A proposal or idea that requires feedback

  
Kind
Security
This is security issue

  
Kind
Studio Request
Requested by a user at the Blender-Studio

  
Kind
Testing
Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 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-pipeline#92
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?