cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Specifying Dashboard label / hierarchy for Triggered Tasks via REST API

IanGiffen
New Contributor

Under normal pipleine excution, where a parent pipeline calls multiple child pipelines, the Dashboard shows the entire execution as one expandable folder, like so:

  • Primary Pipeline
    • Secondary Pipeline 1
      • Tertiary Pipeline 1
      • Tertiary Pipeline 2
    • Secondary Pipeline 2
      etcโ€ฆ
      And we know we can specify the Execution Label on each Pipeline Execute Snap so that โ€œTertiary Pipeline 1โ€ could be displayed as โ€œLog Pipeline (Tertiary Pipeline 1)โ€

However, if we change our architecture to instead call each child as a REST API Triggered Task, the dashboard no longer represents the hierarchy, as each execution is its own separate instance and in reverses calling order like so:

  • Secondary Pipeline 2
  • Tertiary Pipeline 2
  • Tertiary Pipeline 1
  • Secondary Pipeline 1
  • Primary Pipeline

We were wondering if there is anyway a pipeline can set itโ€™s own execution label as one of itโ€™s executing parameters?

For example, if we had a unique session key, each pipeline could modify itโ€™s execution label to include the session ID like so:

  • SESSION A Secondary Pipeline 2
  • SESSION A Tertiary Pipeline 2
  • SESSION A Tertiary Pipeline 1
  • SESSION A Secondary Pipeline 1
  • SESSION A Primary Pipeline

Thank you!

0 REPLIES 0