Pipeline Configurations

Hello,

I am a new pipeline TD trying to set up a pipeline for a VFX workflow, mainly using Nuke X, Nuke Studio, Hiero, Maya and Flow Production Tracking. I have a pipeline set up for a test project in Flow Production Tracking and it seems to be working smoothly. Now, I want to test the pipeline with a new project but when I open the Flow Production Tracking desktop app and open the new project I am not able to open Nuke X or any of the other DCC applications. I am not sure how I can take my existing pipeline and use it for new projects. Does anyone know how I can use the existing one in this new test and other future projects? Also if anyone has any resources or tips for a beginner pipeline TD I would appreciate a great deal.

PD: In my TEST_TVSHOW project it seems to be working as this is where I first set up the pipeline and ran all my tests. In this new TestProject2 I can open some apps but still not all of them, and in another project I cant open anything. In most of the other projects in my Flow Production Tracking page I can only “Publish” but not open any of the DCC apps.

Can you run through the steps you took to set it up? What did you customise?

Hi Patrick,

In my TEST_TVSHOW project I set it up to handle exports from Nuke Studio and publishing from Nuke X to Shotgrid. In the new TestProject2 I basically copied the folder with the pipeline configuration of TEST_TVSHOW on my drive and named the copy TestProject2. Then in the shorgrid pipeline configuration page I added the path to the TestProject2 directory. Before doing this I could only see the “publish” option in the desktop app. Now I can at least launch Hiero and other DCCs but still not Nuke and Nuke Studio. I’m not sure if my explanation was clear enough but is this approach correct?

did you restart sg desktop? sometimes the caching of apps fails.
Can you share the customisations to your app_locations.yml and any other settings?

Yes, but it still opens as shown in the pictures in the earlier post. Do you mean the app_locations.yml file from the toolkit of TEST_TVSHOW?

Did you actually kill the task, closing the sg-desktop app with the close button on the top right just minimises it.
Can you share your console log, with and without debug logging enabled.
Yes, the app_locations.yml.

No, I closed it by clicking the lower right corner and quiting the desktop app.
Sadly I cannot share .yml files on this platform as it is not supported but I’d be happy to get in touch if you have some free time to clear this up as I am trying to get this pipeline up and running ASAP. Thank you for the help either way

What platform are you running on?

You are not pointing your descriptor to the correct folder.
It needs to point to the root folder of the config you are editing.

1 Like

This community shotgrid page does not support uploading .yml files

As someone who has setup alot of configs at the most basic level, my best recommendation is to start from scratch and setup 1 config for all your projects right now.

  1. Delete the “Pipeline Config” and rerun the “Advanced Project Setup” wizard which will create one Pipeline Config.

  2. You might get a Tank Name error so you will need to delete that before re running the setup wizard. You can find the tank name on the Projects page as a field. Its just a text field. Select it and delete the text.

  3. Now run the advanced project setup.

  4. When going through the options choose “Create Uploaded Config” which puts in your site instead of on disk. I prefer this because of performance and cleanliness. (IMO this should be the default option).

  5. This new Pipeline Config will be linked to your current Project.

  6. To use it on other proejcts navigate to the Pipeline Config page and delete the project name in the project field so it has no project. Now it should work for all projects! (You will just have to create a tank name for other projects manually, just add text in the tank name field on the Project, the tank name i think can be anything but do the project name, lowercase, underscores instead of spaces)

Duplicating the config folders on disk is a recipe for a mess in my opinion.

Once you have a new config uploaded, you can setup a process for managing its changes (using git for example) and packaging it back up.

This is 100% my opinion and may not be the best way but i think its probably the simplest.

Also to add to this, please add your configs to a Git Repo, be it on Github, Gitlab or Bitbucket, but please track your changes in git.

Github offers free private repositories, even for organisations.