From the upstream issue: https://github.com/openshift-pipelines/pipelines-as-code/issues/1696

Description:
In Bitbucket, the build status does not change if a PipelineRun is manually deleted by the user (in the OpenShift Web Console for example). Currently, the status only updates if the pipeline is successfully completed or canceled. However, if the PipelineRun is deleted, the status remains "in progress" indefinitely.

Desired Behavior:
When a PipelineRun is deleted by the user, the build status in Bitbucket should be updated accordingly, indicating that the pipeline no longer exists and is not in progress --> status Failed.

Background (Required)

Comment Emil: check if the case is specific to BitBucket or if it happens with all providers

<Describes the context or background related to this story>

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met