PipelineRun cleanup and cancelation

[r0bj]

To be able to cleanup old (finished) PipelineRuns, do I need to create some custom cronjob to do so? Or is there any other native way of cleaning it (some sort of PipelineRun retention policy)?

The same question is for with pipeline cancelation: a PipelineRun triggered by EventListener (let's say it's testing github PR). To cancel first PipelineRun (still running) when another PipelineRun of the same type was triggered, do I need to do it manually (eg. using kubectl from inside task using method from https://tekton.dev/docs/pipelines/pipelineruns/#cancelling-a-pipelinerun)? Or is there some native way using special parameters?
Some Pipelines need to be executed as single at a time (due to eg. shared volumes, etc.).

/kind question
/kind feature

[jlpettersson]

To be able to cleanup old (finished) PipelineRuns, do I need to create some custom cronjob to do so? Or is there any other native way of cleaning it (some sort of PipelineRun retention policy)?

Yes, there is an issue about creating such a CronJob in tektoncd/experimental#479

This comes up often. We could document that Tekton does not currently have functionality for this.

Also related #2332

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

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.