PipelineRun and TaskRun Status

[jerop]

Overview

As discussed in API working group on 02/22 (notes | recording), we need to revisit the design of the Status sections of PipelineRuns and TaskRuns

We agreed that we need to rework the Status sections to be at par with the Spec sections of the API as we work towards V1 release

Problems

Problems in the Status sections include:

• excessive updates
• embedding the TaskRun and Run status in the PipelineRun status
  • takes up a lot of space
  • concern when supporting Pipelines in Pipelines
  • figure out how Results can help
• lack of documentation of the Status; few details in PipelineRun and TaskRun docs

Please share other issues you may have with Status

References

• PipelineRun Status bloat and excessive updates #3140
• Design result reporting to to Result Store #454
• Towards v1 API #3548
• API working group meeting notes

/cc @tektoncd/core-maintainers

[vdemeester]

embedding the TaskRun and Run status in the PipelineRun status

* takes up a lot of space

* concern when supporting [`Pipelines` in `Pipelines`](https:/tektoncd/experimental/pull/705)

* figure out how [`Results`](https:/tektoncd/results) can help

One thing to consider here is that having the spec used in the status allows us to have a finite source of truth of what was used for that run. Without it, we have no way, while looking back at some runs, to know for sure what what the definition of the pipeline or the task executed. In addition, even though we are not taking advantage of this today, this could allow us to reduce the number of "fetching the definiton spec" (from the cluster, from the oci image, …) as the information is already available in the status.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[jerop]

/lifecycle frozen

in the 1.0 roadmap - #3548

[lbernick]

/assign

[lbernick]

/close

TEP-0100 has now been implemented, and documentation of status is being tracked in #4660.

[tekton-robot]

@lbernick: Closing this issue.

In response to this:

/close

TEP-0100 has now been implemented, and documentation of status is being tracked in #4660.

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.