Pipeline Resources Redesign #1673
Comments
ghost
added
the
Epic
ghost
mentioned this issue
ghost
mentioned this issue
|
PipelineResources have a big surface area so we've started to break the constituent pieces into their own deliverables. We've had good success and feedback so far as these features have been added. Workspaces and Task Results are two big chunks of work that support use cases we previously covered with PipelineResources. As we pull these pieces into their own designs and implementations we're also thinking about how we could, in the future, package them all back up into something like PipelineResources that uses all these features but limits the configuration that users have to do. Certainly this won't happen before beta but we're still considering possibilities here. |
With the addition of workspaces and results, we are exploring a world without PipelineResources! (see tektoncd/pipeline#1673) To that end, this commit adds a Task that does the same things as the PullRequest PipelineResource. It still uses the same underlying image, pullrequest-init, which is currently built and published as part of the Tekton Pipelines release, but which one day may be in another repo and published separately. This also includes a "sample" which uses the Task to post a comment on an existing known PR - the only requirement to run it is a secret that contains a github token. Part of tektoncd#95
With the addition of workspaces and results, we are exploring a world without PipelineResources! (see tektoncd/pipeline#1673) To that end, this commit adds a Task that does the same things as the PullRequest PipelineResource. It still uses the same underlying image, pullrequest-init, which is currently built and published as part of the Tekton Pipelines release, but which one day may be in another repo and published separately. This also includes a "sample" which uses the Task to post a comment on an existing known PR - the only requirement to run it is a secret that contains a github token. Part of tektoncd#95
With the addition of workspaces and results, we are exploring a world without PipelineResources! (see tektoncd/pipeline#1673) To that end, this commit adds a Task that does the same things as the PullRequest PipelineResource. It still uses the same underlying image, pullrequest-init, which is currently built and published as part of the Tekton Pipelines release, but which one day may be in another repo and published separately. This also includes a "sample" which uses the Task to post a comment on an existing known PR - the only requirement to run it is a secret that contains a github token. Part of tektoncd#95
With the addition of workspaces and results, we are exploring a world without PipelineResources! (see tektoncd/pipeline#1673) To that end, this commit adds a Task that does the same things as the PullRequest PipelineResource. It still uses the same underlying image, pullrequest-init, which is currently built and published as part of the Tekton Pipelines release, but which one day may be in another repo and published separately. This also includes a "sample" which uses the Task to post a comment on an existing known PR - the only requirement to run it is a secret that contains a github token. Part of #95
|
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
|
/remove-lifecycle rotten |
|
@vdemeester: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
tekton-robot
added
lifecycle/frozen
vdemeester
added
the
area/roadmap
ghost
mentioned this issue
afrittoli
added
the
kind/feature
|
@jerop @vdemeester @afrittoli @pritidesai should we keep this issue open? I think with TEP-0074 we know where we want to go with PipelineResources |
|
Yeah I think we can close 😇 |
|
/close |
|
@lbernick: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What is this thing?
This is a tracking issue / epic for all of the ongoing pipeline resources investigation, design and proof-of-concept work.
Existing Design Work and Feature Requests
Existing PipelineResource Problems
Design Docs Without A Home Anywhere Else
The text was updated successfully, but these errors were encountered: