Epic Goal

Enable chaining pipeline executions in order to run a pipeline upon completion of another pipeline

An example would be to start the integration tests pipeline (B) for a microservice upon completion of the build pipeline (A) for that microservice, and then trigger the whole application system test pipeline that deploys a number of microservices and runs tests against them (C): A --> B --> C

Why is this important?

Applications are composed of many components and there are often multiple pipelines that own part of CI and app delivery at both a microservice level and the who application level. Therefore, customers need a way to define a graph of dependencies between the these pipelines to ensure a certain order of execution that is meaningful for that specific application. 

Acceptance Criteria 

• Within a single Git repository
  • User can specify pipeline B run upon completion of pipeline A in the same repository 
  • User can specify the conditions for starting pipeline B
    • Upon completion
    • Upon successful completion
• Between Git repositories
  • User can specify pipeline B in Git repository B to run upon completion of  pipeline A in Git repository A
  • User can specify the conditions for starting pipeline B
    • Upon completion
    • Upon successful completion

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment