Skip to content

docs(ci): document release smoke testing process#4449

Merged
openshift-merge-bot[bot] merged 2 commits intoredhat-developer:mainfrom
gustavolira:RHIDP-8640
Mar 24, 2026
Merged

docs(ci): document release smoke testing process#4449
openshift-merge-bot[bot] merged 2 commits intoredhat-developer:mainfrom
gustavolira:RHIDP-8640

Conversation

@gustavolira
Copy link
Copy Markdown
Member

@gustavolira gustavolira commented Mar 23, 2026

Summary

  • Adds .ci/release-smoke-testing.md documenting how to run the CI test suite against productized RHDH images for release validation
  • Covers: overriding image variables, updating values files, running additional test suites, testing on custom clusters, and the [skip-build] tip
  • Based on the process used in [TESTING DO NOT MERGE] Test rhdh 1.9 211 #4431

Jira

https://redhat.atlassian.net/browse/RHIDP-8640

Test plan

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci openshift-ci bot requested review from josephca and rostalan March 23, 2026 21:54
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@gustavolira gustavolira changed the title RHIDP-8640: Document release smoke testing process docs(ci): RHIDP-8640 document release smoke testing process Mar 23, 2026
@github-actions
Copy link
Copy Markdown
Contributor

The container image build workflow finished with status: cancelled.

@sonarqubecloud
Copy link
Copy Markdown

@gustavolira gustavolira changed the title docs(ci): RHIDP-8640 document release smoke testing process docs(ci): document release smoke testing process Mar 23, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Image was built and published successfully. It is available at:

Comment thread .ci/release-smoke-testing.md
@josephca
Copy link
Copy Markdown
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm label Mar 24, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 30f6369 into redhat-developer:main Mar 24, 2026
15 of 18 checks passed
Copy link
Copy Markdown
Member

@zdrapela zdrapela left a comment

Choose a reason for hiding this comment

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

@gustavolira @josephca
Have you guys tried #4355? Did it work for you, or do you have any ideas for improvement? I believe it's a superior way of triggering jobs with the option to override the image, rather than opening a PR with specific values.

Comment on lines +30 to +57
## Step 2: Override Image in `values_showcase.yaml`

Edit `.ci/pipelines/value_files/values_showcase.yaml` and update the `upstream.backstage.image`
section:

```yaml
upstream:
backstage:
image:
pullPolicy: Always
registry: quay.io
repository: rhdh/rhdh-hub-rhel9 # was: rhdh-community/rhdh
tag: "1.9-211" # was: next-1.9
```

## Step 3: Override Image in `values_showcase-rbac.yaml`

Apply the same image changes in `.ci/pipelines/value_files/values_showcase-rbac.yaml`:

```yaml
upstream:
backstage:
image:
pullPolicy: Always
registry: quay.io
repository: rhdh/rhdh-hub-rhel9 # was: rhdh-community/rhdh
tag: "1.9-211" # was: next-1.9
```
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

These steps are completely redundant. They are basically placeholders which are getting overriden by helm upgrade -i which uses this function for params:

helm::get_image_params() {
local params=""
# Add image repository
params+="--set upstream.backstage.image.repository=${QUAY_REPO} "
# Add image tag
params+="--set upstream.backstage.image.tag=${TAG_NAME} "
echo "${params}"
return 0
}

It's actually pretty misleading, and we should replace them or delete them from the value files.

Copy link
Copy Markdown
Member

@zdrapela zdrapela Mar 25, 2026

Choose a reason for hiding this comment

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

PR to remove them as a proof: #4457

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants