Epic Goal

Many organisations create a set of golden pipelines that are managed centrally and provided to app dev teams to run for their applications. The app dev teams need the ability to import an existing golden pipeline (e.g. from a Git repo) as a part of their pipeline and execute the tasks from the golden pipeline as if the tasks existed in their own pipeline. Furthermore, the app dev teams need to be able to author their pipeline with tasks that should execute before and after the imported golden pipelines in order to adjust it to the needs of their application.

Resolvers today provide the ability to reference a remote pipeline (e.g. in a Git repo), however that pipeline would execute in its entirety and the app dev team do not have the ability to modify (add tasks before or after it) the golden pipeline.

Why is this important?

In order to enable platform teams to provide a library of curated and lifecycled pipeline definitions for the app dev team and at the same time to provide flexibility to the app dev teams to create their own pipelines by extending the curated pipeline, instead of having to entirely replace it in order to make any modifications. 

Acceptance Criteria

• A pipeline (caller) can reference one or several pipelines (imported)
• The caller pipeline can add tasks before and after each imported pipeline
• The tasks in the imported pipeline execute as if the were tasks within the caller pipeline

Previous Work (Optional):

• Experimental: pipeline in pipeline
• Tekton resolvers