Story (Required)

Pipelines-as-Code (PAC) allows users to use custom tags (e.g., {}{{target_branch{}}}, {}{{sender{}}}, {}{{body{}}}) within their .tekton manifests. These tags are dynamically replaced by PAC during the event processing phase. To ensure the stability of this feature in OpenShift Pipelines, we need to implement automated integration tests in the downstream release-tests repository that validate the correct expansion of these variables during a real GitHub/GitLab event flow

Approach (Required)

Add test to release-test repo

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

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