Skip to content

Add release test ginkgo pipeline - #27576

Open
pramodbindal wants to merge 1 commit into
mainfrom
pb/ginkgo
Open

Add release test ginkgo pipeline#27576
pramodbindal wants to merge 1 commit into
mainfrom
pb/ginkgo

Conversation

@pramodbindal

Copy link
Copy Markdown
Member

No description provided.

Copilot AI lite review requested due to automatic review settings August 14, 2026 06:07
@openshift-ci

openshift-ci Bot commented Aug 14, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pramodbindal

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Label for Approved PRs label Aug 14, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR replaces the prior Konflux Tekton “bundle e2e” pipeline with a new Ginkgo-oriented release-test pipeline definition under .konflux/release-tests-ginkgo/, including a reusable Task to run the release tests against an ephemeral Hypershift cluster.

Changes:

  • Removes the legacy .konflux/tekton/bundle-e2e-pipeline.yaml pipeline.
  • Adds a new reusable Tekton Task to fetch and run the release-tests-ginkgo suite.
  • Adds a new Tekton Pipeline that provisions EAAS + cluster, installs the operator, runs multiple release-test suites, and verifies aggregate status.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
.konflux/tekton/bundle-e2e-pipeline.yaml Removes the old bundle E2E pipeline definition.
.konflux/release-tests-ginkgo/task-e2e-pipeline.yaml Adds a Task to clone and execute release tests (Ginkgo-oriented).
.konflux/release-tests-ginkgo/release-test-pipeline.yaml Adds the new end-to-end release test Pipeline (provision, install, run suites, final status check).
Suppressed comments (4)

.konflux/release-tests-ginkgo/release-test-pipeline.yaml:134

  • The extract-and-pick-version step writes the step result to /tekton/steps/step-extract-and-pick-version/..., but the step name is extract-and-pick-version. This will prevent $(steps.extract-and-pick-version.results.version) from being populated, so cluster creation may receive an empty version.
              # Write result for create-cluster step
              mkdir -p /tekton/steps/step-extract-and-pick-version/results
              echo -n "$VERSION" | tee /tekton/steps/step-extract-and-pick-version/results/version

.konflux/release-tests-ginkgo/release-test-pipeline.yaml:228

  • The CatalogSource YAML sets updateStrategy: and registryPoll: to null and places interval at the wrong level. This likely makes the applied manifest invalid or ignored by OLM. interval should be nested under updateStrategy.registryPoll.
                  updateStrategy:
                  registryPoll:
                  interval: 30m

.konflux/release-tests-ginkgo/release-test-pipeline.yaml:549

  • This step runs under #!/bin/sh but uses [[ ... ]], which is not POSIX and can fail if /bin/sh is not bash. Use [ ... ] (or switch the shebang to bash).
              if [[ "$(params.aggregateStatus)" != "Succeeded" ]]; then

.konflux/release-tests-ginkgo/task-e2e-pipeline.yaml:138

  • This script uses bash-specific options (set +H / set -H). Without a bash shebang, Tekton may run it under /bin/sh, which can fail depending on the image's /bin/sh implementation. Add an explicit bash shebang at the top of the script block.
        # Some of the tests fail on specific OCP versions
        set +H
        tags="$(params.TAGS),!(skip-$OCP_VERSION | to-do)"
        set -H

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +28 to +29
- name: GIT_RELEASE_TESTS_BRANCH
default: master
Comment on lines +15 to +16
- description: Namespace where the the Operator bundle will be deployed.
name: NAMESPACE
Comment on lines +24 to +25
- name: FAIL_ON_ERROR
default: "false"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Label for Approved PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants