chore(tech-radar): re-trigger e2e to generate coverage [do not merge] by gustavolira · Pull Request #2678 · redhat-developer/rhdh-plugin-export-overlays

gustavolira · 2026-06-25T13:04:20Z

Throwaway re-trigger PR — do not merge; close after the run.

tech-radar was merged with the e2e-test-utils 2.1.0 bump + coverage anchors, but its e2e (/test e2e-ocp-helm) never ran before merge, so no coverage was ever uploaded and the e2e-tech-radar flag doesn't exist.

This PR only triggers the e2e. Steps:

/publish
/test e2e-ocp-helm → wait for "✅ Passed E2E Tests"
We grab the coverage from the run, commit coverage-snapshots/tech-radar.lcov in a separate PR, and close this one.

🤖 Generated with Claude Code

gustavolira · 2026-06-25T13:05:03Z

/publish

github-actions · 2026-06-25T13:10:31Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

✅ Published container images:

ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar:pr_2678__1.17.0
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar-backend:pr_2678__1.16.0

Backstage Compatibility Check

✅ All workspaces are compatible with the target Backstage version (1.49.4).

No action required.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

github-actions · 2026-06-25T13:13:44Z

✅ Smoke tests workflow passed. All plugins loaded successfully.

github-actions · 2026-06-25T13:49:30Z

Successfully updated file versions.jsonfrom branch main into this PR in commit 5da512b

github-actions · 2026-06-25T13:57:59Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

✅ Published container images:

ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar:pr_2678__1.17.0
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar-backend:pr_2678__1.16.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.52.0).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/tech-radar	1.49.2	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository using the /override-backstage command which will add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

github-actions · 2026-06-25T14:26:00Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

✅ Published container images:

ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar:pr_2678__1.17.0
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar-backend:pr_2678__1.16.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.52.0).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/tech-radar	1.49.2	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository using the /override-backstage command which will add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

rhdh-test-bot · 2026-06-25T18:17:05Z

❌ Failed E2E Tests - `tech-radar`

gustavolira · 2026-06-26T17:10:04Z

/update-commit

github-actions · 2026-06-26T17:11:30Z

Update Commit workflow has completed with success.

github-actions · 2026-06-26T17:16:41Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

✅ Published container images:

ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar:pr_2678__1.17.0
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar-backend:pr_2678__1.16.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.52.0).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/tech-radar	1.49.2	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository using the /override-backstage command which will add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

rhdh-test-bot · 2026-06-26T17:48:25Z

✅ Passed E2E Tests - `tech-radar`

codecov · 2026-06-26T17:48:50Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.38%. Comparing base (bf1095d) to head (cbdfd88).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

Flag	Coverage Δ
e2e-tech-radar	`72.85% <ø> (?)`

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

gustavolira · 2026-06-26T19:04:03Z

/override-backstage

gustavolira · 2026-06-26T19:04:53Z

/publish

github-actions · 2026-06-26T19:05:31Z

Override Backstage workflow partially completed.

backstage.json created/updated (commit: 68853d0)
Metadata refresh failed — see workflow run

The backstage.json override to 1.52.0 was applied, but metadata files (OCI tags, supportedVersions) were not updated automatically. You can retry with /override-backstage or manually update the metadata files.

github-actions · 2026-06-26T19:10:52Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

✅ Published container images:

ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar:pr_2678__1.17.0
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar-backend:pr_2678__1.16.0

Backstage Compatibility Check

✅ All workspaces are compatible with the target Backstage version (1.52.0).

No action required.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

github-actions · 2026-06-26T19:14:46Z

✅ Smoke tests workflow passed. All plugins loaded successfully.

rhdh-test-bot · 2026-06-26T19:23:57Z

✅ Passed E2E Tests - `tech-radar`

gustavolira · 2026-06-29T14:26:49Z

/test e2e-ocp-helm

Temporary marker PR — tech-radar merged its rollout (2.1.0 + anchors) without running /test e2e-ocp-helm, so no coverage was collected. This triggers /publish + /test; the snapshot is committed separately and this PR is closed after the run. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

gustavolira · 2026-06-29T14:38:37Z

/publish

github-actions · 2026-06-29T14:43:50Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

✅ Published container images:

ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar:pr_2678__1.20.0
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-tech-radar-backend:pr_2678__1.19.0

Backstage Compatibility Check

✅ All workspaces are compatible with the target Backstage version (1.52.0).

No action required.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

github-actions · 2026-06-29T14:46:58Z

✅ Smoke tests workflow passed. All plugins loaded successfully.

rhdh-test-bot · 2026-06-29T15:04:35Z

✅ Passed E2E Tests - `tech-radar`

…ip ci]

gustavolira · 2026-06-29T16:30:16Z

Closing — this was the throwaway test vehicle for the auto-refresh workflow (#2717). It did its job: the e2e passed, the refresh-coverage-snapshot workflow fired and committed coverage-snapshots/tech-radar.lcov automatically (byte-identical to the manual snapshot in #2716). The marker file here shouldn't land on main; tech-radar coverage lands via #2716 instead.

sonarqubecloud · 2026-06-29T16:31:05Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Captured from the passing tech-radar e2e run on PR #2678 (208/236 lines). PR-head uploads don't carry to main across squash-merge, so the seed workflow re-uploads this snapshot to main HEAD under the e2e-tech-radar flag — making the flag show a real report on the default branch. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

gustavolira requested review from a team, gashcrumb and kadel as code owners June 25, 2026 13:04

github-actions Bot added mandatory-workspace PR affects a workspace with required plugins for releases workspace-update PR modifies files in an existing workspace labels Jun 25, 2026

gustavolira mentioned this pull request Jun 26, 2026

chore(coverage): seed tech-radar e2e coverage snapshot (88.13%) #2716

Merged

gustavolira and others added 2 commits June 29, 2026 11:37

chore(tech-radar): override backstage compatibility to 1.52.0

1d8c0ef

gustavolira force-pushed the chore/retrigger-coverage-tech-radar branch from cbdfd88 to 1d8c0ef Compare June 29, 2026 14:38

chore(coverage): refresh tech-radar snapshot from passing e2e run [sk…

e61fa2c

…ip ci]

gustavolira closed this Jun 29, 2026

gustavolira deleted the chore/retrigger-coverage-tech-radar branch June 29, 2026 16:30

Uh oh!

Conversation

gustavolira commented Jun 25, 2026

Uh oh!

gustavolira commented Jun 25, 2026

Uh oh!

github-actions Bot commented Jun 25, 2026

Publishing process

Backstage Compatibility Check

Metadata Validation

Uh oh!

github-actions Bot commented Jun 25, 2026

Uh oh!

github-actions Bot commented Jun 25, 2026

Uh oh!

github-actions Bot commented Jun 25, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions Bot commented Jun 25, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

rhdh-test-bot commented Jun 25, 2026

❌ Failed E2E Tests - tech-radar

Uh oh!

gustavolira commented Jun 26, 2026

Uh oh!

github-actions Bot commented Jun 26, 2026

Uh oh!

github-actions Bot commented Jun 26, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

rhdh-test-bot commented Jun 26, 2026

✅ Passed E2E Tests - tech-radar

Uh oh!

codecov Bot commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

gustavolira commented Jun 26, 2026

Uh oh!

gustavolira commented Jun 26, 2026

Uh oh!

github-actions Bot commented Jun 26, 2026

Uh oh!

github-actions Bot commented Jun 26, 2026

Publishing process

Backstage Compatibility Check

Metadata Validation

Uh oh!

github-actions Bot commented Jun 26, 2026

Uh oh!

rhdh-test-bot commented Jun 26, 2026

✅ Passed E2E Tests - tech-radar

Uh oh!

gustavolira commented Jun 29, 2026

Uh oh!

gustavolira commented Jun 29, 2026

Uh oh!

github-actions Bot commented Jun 29, 2026

Publishing process

Backstage Compatibility Check

Metadata Validation

Uh oh!

github-actions Bot commented Jun 29, 2026

Uh oh!

rhdh-test-bot commented Jun 29, 2026

✅ Passed E2E Tests - tech-radar

Uh oh!

gustavolira commented Jun 29, 2026

Uh oh!

sonarqubecloud Bot commented Jun 29, 2026

Quality Gate passed

Uh oh!

Reviewers

❌ Failed E2E Tests - `tech-radar`

✅ Passed E2E Tests - `tech-radar`

codecov Bot commented Jun 26, 2026 •

edited

Loading

✅ Passed E2E Tests - `tech-radar`

✅ Passed E2E Tests - `tech-radar`