Cancel existing pipeline runs when a new pipeline run is triggered (OpenShift Platform). How to do this?

[aksth]

I am using OpenShift Container Platform's Web Console to manage my Tekton Pipelines. I have a pipeline that is triggered when a commit is performed in the master branch, controlled via an event listener. When I make multiple commits simultaneously, multiple pipeline runs are created and they run in parallel to each other. But what I want is to cancel the existing pipeline runs when a new commit is made to the master branch so that only the latest pipeline run exists. Basically, I only want a single pipeline run for a pipeline that would correspond to the latest commit in the master branch. How to do this?

[vdemeester]

@aksth 👋🏼 https://hackmd.io/GK_1_6DWTvSiVHBL6umqDA and tektoncd/community#716 might be of interest to you 👼🏼

[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.

[lbernick]

design in progress -- https://github.com/tektoncd/community/blob/main/teps/0120-canceling-concurrent-pipelineruns.md

[vdemeester]

remove-lifecycle stale

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
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 rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/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 with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/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.