TEP-0056: Pipelines in Pipelines - Add Use Case #498
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In tektoncd/pipeline#4067, @mjgkaastrupandersen shares an additional use case for pipelines in pipelines. In the issue, they describe how they need a gateway task or grouping of pipelines to simplify specifying that a set of tasks all need to wait for another set of tasks to complete execution. In this change, we add that use case to [TEP-0056: Pipelines in Pipelines](https://github.com/tektoncd/community/blob/main/teps/0056-pipelines-in-pipelines.md).
tekton-robot
added
the
kind/tep
tekton-robot
added
the
size/M
vdemeester
approved these changes
Aug 17, 2021
tekton-robot
added
the
approved
|
/assign @sbwsg @vdemeester |
ghost
approved these changes
Aug 24, 2021
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg, vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
jerop
added a commit
to jerop/community
that referenced
this pull request
May 4, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 In this change, we build on that problem statement to include the experiences and learnings using the experimental `Pipelines` in `Pipelines` `Custom Task` over the past several months. In summary, the motivation for `Pipelines` in `Pipelines` include composability, reusability, failure strategies, skipping strategies, data locality & pod overhead and secure software supply chain.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 4, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 In this change, we build on that problem statement to include the experiences and learnings using the experimental `Pipelines` in `Pipelines` `Custom Task` over the past several months. In summary, the motivation for `Pipelines` in `Pipelines` include composability, reusability, failure strategies, skipping strategies, data locality & pod overhead and secure software supply chain.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 5, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 In this change, we build on that problem statement to include the experiences and learnings using the experimental `Pipelines` in `Pipelines` `Custom Task` over the past several months. In summary, the motivation for `Pipelines` in `Pipelines` include composability, reusability, failure strategies, skipping strategies, data locality & pod overhead and secure software supply chain.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 5, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 In this change, we build on that problem statement to include the experiences and learnings using the experimental `Pipelines` in `Pipelines` `Custom Task` over the past several months. In summary, the motivation for `Pipelines` in `Pipelines` include composability, reusability, failure strategies, skipping strategies, data locality & pod overhead and secure software supply chain.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 6, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 In this change, we build on that problem statement to include the experiences and learnings using the experimental `Pipelines` in `Pipelines` `Custom Task` over the past several months. In summary, the motivation for `Pipelines` in `Pipelines` include composability, reusability, failure strategies, skipping strategies, data locality & pod overhead and secure software supply chain.
tekton-robot
pushed a commit
that referenced
this pull request
May 6, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - #374 - #498 In this change, we build on that problem statement to include the experiences and learnings using the experimental `Pipelines` in `Pipelines` `Custom Task` over the past several months. In summary, the motivation for `Pipelines` in `Pipelines` include composability, reusability, failure strategies, skipping strategies, data locality & pod overhead and secure software supply chain.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 9, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`. In summary, we plan to support `PipelineRef` and `PipelineSpec` only initially. The API design is extensible to support other fields related to creating a `PipelineRun`.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 9, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`. In summary, we plan to support `PipelineRef` and `PipelineSpec` only initially. The API design is extensible to support other fields related to creating a `PipelineRun`.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 9, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`. In summary, we plan to support `PipelineRef` and `PipelineSpec` only initially. The API design is extensible to support other fields related to creating a `PipelineRun`.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 9, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`. In summary, we plan to support `PipelineRef` and `PipelineSpec` only initially. The API design is extensible to support other fields related to creating a `PipelineRun`.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 24, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 24, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 24, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 24, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 24, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
May 25, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
Jun 6, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
Jun 6, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
Jun 6, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
Jun 7, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
Jun 7, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
jerop
added a commit
to jerop/community
that referenced
this pull request
Jun 13, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - tektoncd#374 - tektoncd#498 - tektoncd#698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
tekton-robot
pushed a commit
that referenced
this pull request
Jun 22, 2022
Today, users can define and execute `Tasks` and `Custom Tasks` in `Pipelines`. In this TEP, we propose allowing users to define and execute `Pipelines` in `Pipelines`, alongside `Tasks` and `Custom Tasks`. We previously described the motivation for this TEP in: - #374 - #498 - #698 In this change, we add an overview of the proposal which includes the API changes to the specification and status of `Pipelines`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In tektoncd/pipeline#4067, @mjgkaastrupandersen shares an additional use case for pipelines in pipelines. In the issue, they describe how they need a gateway task or grouping of pipelines to simplify specifying that a set of tasks all need to wait for another set of tasks to complete execution. In this change, we add that use case to TEP-0056: Pipelines in Pipelines.
Thank you for sharing your use case @mjgkaastrupandersen! 😀
/kind tep