naxlatin.blogg.se - Publisher plus templates

Therefore if the version number were inherited from the working file, it would be inconsistent. The reason behind this choice, is that often the same asset is worked on in several tasks. To represent this, I created the PublishedItem entity. Published files are indeed connected with a task (in which they are generated by it), but in fact they represent the evolution of an asset (asset in a generic sense, not a shotgun asset). Working files represent the evolution of a task. Yes I do want to have publishes which are versioned separately from working files. How should I go about this? Do I have to change UI, hooks and core modules of tk-multi-publish2 ? Maybe I’m misunderstanding what the publisher is supposed to do, but I really wasn’t expecting it to save any files using the maya_asset_work path.

When I click on the Publish button, it still saves a file in my maya_asset_work path (plus, it overwrites the latest version and creates a new one…).

Should I change the code for the UI or is there some other way to pass on this information (i.e. This is defined in the templates.yml, but the publisher doesn’t know where to take this information from, as the ui does not let me choose any additional information.

I want my published files to be organized by PublishedItem (and then versioned).

However, I’m having two issues at this point: Then, when I load the publisher, it automatically understands which context I’m in and passes it to the publish functions to resolve the template. I managed to correctly get the tk-multi-workfiles2 to save the task files in the right location.

Now, I’ve edited the folder schema, the templates.yml and the various environment yml files to reflect these changes, but I still get errors whenever I try to publish something.įor the sake of this example, let’s say I’m using Maya and I’m working on an asset task (so I’m in the asset_step ). Published files - represent the evolution of PublishedItems Īnd eventually I want to be able to keep track of dependencies between PublishedItems. Work files - represent the evolution of Tasks

I’ve added a “Published Items” field to the Task entity, and a “Tasks” field to the PublishedItem entity.īasically the logic that I want to follow is: I’ve created a PublishedItem custom entity to represents the items that I want to publish and that I want to keep track of. I’m trying to customize my pipeline so that published files are handled unrelated from tasks. So apologies in advance for any blasphemies I might be writing in this post! I’m kinda new to SG, and I’m still trying to figure out lots of things.