08 ‐ Pipeliner

We can integrate the dpAutoRigSystem into a pipeline using the Pipeliner settings.

Go to the menu Create/Pipeliner to access it.

Doc5: Pipeline Info

It's a bit technical, but that is how it works:

1. The dpPipelineInfo.json file is the most important file for the pipeline system because it stores all the information about folders, preferences, and settings.
2. Usually, its name and path are in .../maya/scripts/dpAutoRigSystem/Pipeline/dpPipelineSettings.json.
3. If we want to work with a recommended flexible pipeline, we can leave the dpPipelineSettings.json file as the default and create a dpPipelineInfo.json file in the _dpPipeline folder to load assets and get the pipeline data automatically. Here's a good example:

Pipeline Files - Example

• UI:
  • File path: the path and filename to find the dpPipelineInfo.json. (R:/Testing/_dpPipeline/dpPipelineInfo.json)
  • drive: the letter of the drive where we have our project. (R:)
  • studio: the name of the studio. (R:/Testing)
  • project: the name of the project. (R:/Testing/DaniloTest)
  • wip: folder where we have asset files. (R:/Testing/DaniloTest/Rigging/WIP)
  • publish: folder where we export the published rig files. (R:/Testing/DaniloTest/Rigging/Published)
  • toClient: folder where we save the published rig zip file to send it to the client. (R:/Testing/DaniloTest/Data/ToClient)
  • presets: folder to save publishing presets. (R:/Testing/_dpPipeline/dpPresets)
  • addOns: folder to save extra addOn validators. (R:/Testing/_dpPipeline/dpAddOns)
  • finishing: folder to save extra finishing validators. (R:/Testing/_dpPipeline/dpFinishing)
  • hist: folder where the old wip rig files will be stored after publishing the asset. (R:/Testint/DaniloTest/Rigging/WIP/AssetName/dpData/dpHist)
  • old: folder where we put the old published rig files when we publish a new rig version. (R:/Testint/DaniloTest/Rigging/Published/dpOld)
  • dropbox: folder to put the published rig zip file into the Dropbox user integration.
  • webhook: the URL address to call a webhook integration.
  • callback: the file to be called after the publishing process is done.
  • Naming:
    • prefix: adds a prefix to the published rig file name if we want, before the asset name.
    • middle: the added part naming to keep a good convention. We use, for example, _rig_v.
    • suffix: adds a suffix to the published rig file name if we want, after all.
    • model: part of the name expected to compose the model version used in the asset. We use, for example, _m.
    • rig: part of the name expected to compose the rig version. We use, for example, _v.
    • padding: the number of digits we have in the name.
    • capitalize: if we use the first letter as capital and the other not, like Name.
    • upper: if we want to have all capital letters, like NAME.
    • lower: if we want to have all minor letters, like name.
    • That will do something like this for our naming convention:
      • wip rig file name: AssetName_m001_v001.ma
      • published rig file name: AssetName_rig_v001.ma
  • Delivering:
    • deliver: whether the script should process the packaging instructions to make the deliverable files or not.
    • assetDir: check if we have the wip rig file inside of the asset name folder into the wip rig directory like R:/Testing/DaniloTest/Rigging/WIP/**AssetNameFolder**/AssetName_m002_v003.ma.
    • archive: if we want to transfer the old wip rig files to the dpOld folder when the rig is published.
    • dateDir: if we want to create a folder with the date when preparing the file for a client, like R:/Testing/DaniloTest/Data/ToClient/YYYY-MM-DD.
    • zip: if we want to compress the published file into a zip archive.
    • cloud: if we like to make a copy of the published zip file in a cloud directory, for example, Dropbox.
    • imager: create an image with the rigging preview screen capture and this info:
      • i_maya: Maya version.
      • i_version: dpAutoRigSystem version.
      • i_studio: studio name.
      • i_project: project name.
      • i_asset: asset name.
      • i_model: model version.
      • i_wip: wip rig version.
      • i_publish: published rig version.
      • i_date: today date as YYYY-MM-DD.
      • i_degrade: set a nice degrade color to the background.

Doc5: Pipeline Configuration