Epic Goal

• Make sure there exists a midstream nightly testing infrastructure which will help developers automate testing scenarios on when the head from the upstream is updated in downstream repos. The goal of this epic is to release the operator based on an update to the components and run downstream tests agaist it automatically.

Why is this important?

• A lot of time is wasted in manually doing releases and then having the QE team test manually when not necessary as this is something that can be automated. The QE teams efforts can go into engineering and writing automated tests better, instead of manually testing everything.

Scenarios

1. eg: when there is an update in the the tektoncd/pipeline repo at the time the head commit will be updated and downstream automations will update this commit id in "head" file on in the openshift-pipelines/tektoncd-pipeline repository.

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. Understand release process

Previous Work (Optional):

1. https://github.com/openshift-pipelines/plumbing/tree/master

Open questions::

1. Where do we get the infrastructure from ?
   The initial work towards this is going to be into figuring out on what infra can we run this on ?
2. What after ?
   Using LLMs for analysis.

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in the production environment