Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TEP-0142: Enable Step Reusability - Implementation #7259

Closed
20 tasks done
chitrangpatel opened this issue Oct 23, 2023 · 2 comments
Closed
20 tasks done

TEP-0142: Enable Step Reusability - Implementation #7259

chitrangpatel opened this issue Oct 23, 2023 · 2 comments
Assignees

Comments

@chitrangpatel chitrangpatel added this to the Pipelines v0.54 milestone Oct 23, 2023
@chitrangpatel chitrangpatel self-assigned this Oct 23, 2023
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 23, 2023
This PR introduces the StepAction CRD in `v1alpha1`. This is not the complete CRD. As we add support for `params`, `results` etc. we will introduce in follow-up PRs.

It is the first of many implementation PRs as described in issue:  tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 23, 2023
This PR introduces the StepAction CRD in `v1alpha1`. This is not the complete CRD. As we add support for `params`, `results` etc. we will introduce in follow-up PRs.

It is the first of many implementation PRs as described in issue:  tektoncd#7259
@jerop jerop changed the title Implementation StepActions TEP-0142: Enable Step Reusability - Implementation Oct 23, 2023
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 23, 2023
This PR introduces the StepAction CRD in `v1alpha1`. This is not the complete CRD. As we add support for `params`, `results` etc. we will introduce in follow-up PRs.

It is the first of many implementation PRs as described in issue:  tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 23, 2023
This PR introduces the StepAction CRD in `v1alpha1`. This is not the complete CRD. As we add support for `params`, `results` etc. we will introduce in follow-up PRs.

It is the first of many implementation PRs as described in issue:  tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 23, 2023
This PR introduces the StepAction CRD in `v1alpha1`. This is not the complete CRD. As we add support for `params`, `results` etc. we will introduce in follow-up PRs.

It is the first of many implementation PRs as described in issue:  tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 24, 2023
This PR introduces the StepAction CRD in `v1alpha1`. This is not the complete CRD. As we add support for `params`, `results` etc. we will introduce in follow-up PRs.

It is the first of many implementation PRs as described in issue:  tektoncd#7259
tekton-robot pushed a commit that referenced this issue Oct 24, 2023
This PR introduces the StepAction CRD in `v1alpha1`. This is not the complete CRD. As we add support for `params`, `results` etc. we will introduce in follow-up PRs.

It is the first of many implementation PRs as described in issue:  #7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 24, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 25, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 25, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 25, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 25, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 25, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 25, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 25, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 26, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 27, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 27, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 27, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Oct 30, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue tektoncd#7259
tekton-robot pushed a commit that referenced this issue Oct 30, 2023
This PR allows the Step to reference a StepAction CRD deployed on the cluster. This capability is gated behind a feature flag `enable-step-actions`.  Remote resolution of StepActions will be implemented in a follow-up PR.

This is the second item on the implementation Issue #7259
Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Nov 1, 2023
This commit is part of tektoncd#7259. It adds the remote resolution for
StepAction.

Signed-off-by: Yongxuan Zhang [email protected]
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 6, 2023
Following the previous [PR](tektoncd#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This
completes support for params in `StepActions`. This work is part of
issue tektoncd#7259.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 6, 2023
Following the previous [PR](tektoncd#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This PR adds the necessary syntax to `Steps` to pass `params` to `StepActions`. This work is part of
issue tektoncd#7259.
Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Nov 7, 2023
This commit is part of tektoncd#7259. It adds the remote resolution for
StepAction.

Signed-off-by: Yongxuan Zhang [email protected]
Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Nov 7, 2023
This commit is part of tektoncd#7259. It adds the remote resolution for
StepAction.

Signed-off-by: Yongxuan Zhang [email protected]
tekton-robot pushed a commit that referenced this issue Nov 7, 2023
Following the previous [PR](#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This PR adds the necessary syntax to `Steps` to pass `params` to `StepActions`. This work is part of
issue #7259.
Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Nov 7, 2023
This commit is part of tektoncd#7259. It adds the remote resolution for
StepAction.

Signed-off-by: Yongxuan Zhang [email protected]
tekton-robot pushed a commit that referenced this issue Nov 8, 2023
This commit is part of #7259. It adds the remote resolution for
StepAction.

Signed-off-by: Yongxuan Zhang [email protected]
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 8, 2023
Following the previous [PR](tektoncd#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This
completes support for params in `StepActions`. This work is part of
issue tektoncd#7259.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 8, 2023
Following the previous [PR](tektoncd#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This
completes support for params in `StepActions`. This work is part of
issue tektoncd#7259.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 8, 2023
Following the previous [PR](tektoncd#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This
completes support for params in `StepActions`. This work is part of
issue tektoncd#7259.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 8, 2023
Following the previous [PR](tektoncd#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This
completes support for params in `StepActions`. This work is part of
issue tektoncd#7259.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 8, 2023
Following the previous [PR](tektoncd#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This
completes support for params in `StepActions`. This work is part of
issue tektoncd#7259.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 9, 2023
Following the previous [PR](tektoncd#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This
completes support for params in `StepActions`. This work is part of
issue tektoncd#7259.
tekton-robot pushed a commit that referenced this issue Nov 9, 2023
Following the previous [PR](#7317), which introduced Params to the `StepAction` CRD,
this PR integrates `param` usage between `Steps` and `StepActions`. This
completes support for params in `StepActions`. This work is part of
issue #7259.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 10, 2023
This PR introduces the field `Value` in `TaskResults`.
This field is necessary to capture the results produced by `StepActions`
if the Task needs to resolve name conflicts.

This is part of issue tektoncd#7259.
Following this PR, we will add support for extracting StepAction results
via termination message and sidecar logs.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 10, 2023
This PR introduces the field `Value` in `TaskResults`.
This field is necessary to capture the results produced by `StepActions`
if the Task needs to resolve name conflicts.

This is part of issue tektoncd#7259.
Following this PR, we will add support for extracting StepAction results
via termination message and sidecar logs.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 10, 2023
This PR introduces the field `Value` in `TaskResults`.
This field is necessary to capture the results produced by `StepActions`
if the Task needs to resolve name conflicts.

This is part of issue tektoncd#7259.
Following this PR, we will add support for extracting StepAction results
via termination message and sidecar logs.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 10, 2023
This PR introduces the field `Value` in `TaskResults`.
This field is necessary to capture the results produced by `StepActions`
if the Task needs to resolve name conflicts.

This is part of issue tektoncd#7259.
Following this PR, we will add support for extracting StepAction results
via termination message and sidecar logs.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 10, 2023
This PR introduces the field `Value` in `TaskResults`.
This field is necessary to capture the results produced by `StepActions`
if the Task needs to resolve name conflicts.

This is part of issue tektoncd#7259.
Following this PR, we will add support for extracting StepAction results
via termination message and sidecar logs.
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Nov 10, 2023
This PR introduces the field `Value` in `TaskResults`.
This field is necessary to capture the results produced by `StepActions`
if the Task needs to resolve name conflicts.

This is part of issue tektoncd#7259.
Following this PR, we will add support for extracting StepAction results
via termination message and sidecar logs.
tekton-robot pushed a commit that referenced this issue Nov 10, 2023
This PR introduces the field `Value` in `TaskResults`.
This field is necessary to capture the results produced by `StepActions`
if the Task needs to resolve name conflicts.

This is part of issue #7259.
Following this PR, we will add support for extracting StepAction results
via termination message and sidecar logs.
@jerop
Copy link
Member

jerop commented Nov 27, 2023

Thank you @chitrangpatel and @Yongxuanzhang on the hard work here, excited to see this feature in v0.54 🎉

Created #7424 to track the next steps and user feedback

@jerop jerop closed this as completed Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants