THIS HAS BEEN MOVED FROM PLNSRVCE - see https://issues.redhat.com/browse/PLNSRVCE-1182?focusedId=24603295&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-24603295 for rationale as to whether this should even be considered moving forward.

Story (Required)

As a Pipeline Service developer trying to add features to Tekton Results I want to run some of the upstream Tekton Results e2e tests against our Pipeline Service configuration.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

We need to have confidence that changes to Tekton Results don't break Pipeline service, and verify our particular configuration works.

<Describes the context or background related to this story>

Out of scope

<Defines what is not included in this story>

• Adding additional checks/tests to the upstream e2e suite for Tekton Results. This includes adding tests that verify the log behavior works.
• Removing or altering any existing "downstream" e2e tests in the pipeline-service repository.
• Adding e2e tests/pipelines to our fork of Tekton Results
• Updating the RHTAP e2e suite so that it includes Results functionality.

Approach (Required)

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

• Create one or more Tekton tasks that run the upstream Results e2e test, skipping the steps to setup a KinD cluster, database, and deploy the Results apiserver + watcher.
  • Prerequisite: The Tekton Results code that corresponds to the deployed Results images needs to be checked out.
  • Upstream tests set up TLS keypairs - do we need this if the test runs on OpenShift? https://github.com/tektoncd/results/blob/main/test/e2e/01-install.sh#L35-L66
  • A step is needed to create a service account token that the test will utilize. See https://github.com/tektoncd/results/blob/main/test/e2e/01-install.sh#L74-L80
  • Run the test by invoking `go test` - See https://github.com/tektoncd/results/blob/main/test/e2e/e2e.sh#L43
• Add these tasks to one of the following:
  • A new Pipelines as Code PipelineRun that is specific for Tekton Results and OpenShift Pipeline changes
  • The existing Pipelines as Code PipelineRun objects (pull request, merge). For this approach, we should add logic that ensures we only run theses tests if we detect that code in the "tekton-results" or "openshift-pipeline" folders were changed.

Dependencies

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

Acceptance Criteria  (Mandatory)

• Tekton Results e2e tests are run against our Pipeline Service configuration when we change/bump Tekton Results.
• (optional) Tekton Results e2e tests are run against our Pipeline Service configuration when we change/bump OpenShift Pipelines.

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

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