I was wondering if there is a way to separate out the assets from the tasks when batch publishing files from the standalone publisher . For instance if I wanted to republish all of the model tasks in a project due to an update. Currently in the standalone publisher it seems to be that you would have to choose a task for each one of the files in-order for them to go to the proper place.
Part of our current process saves a dcc_state and a publish_tree for the most resent publish. would it be a better idea to make an app that runs all the publishes using these files?
so if I had a list of 20 assets that I needed to republish I would have to select the task for each of these assets instead of just selecting the overall task such as ‘model’ and have it just recognize that it is a model publish for all of these assets.
Not sure if there is a way to publish by task type with the Standalone publisher.For batch publishing with it, I think the post below may bring you some inspiration.