fix(github): e2e test config paths

[jrichter1]

point the tests to the appropriate app config files, since they got moved out of the default location

[jrichter1]

/publish

[sonarqubecloud]

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

[jrichter1]

/test e2e-ocp-helm

[github-actions]

Publish workflow has completed with failure.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-github-actions:pr_2301__0.21.0
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-github-issues:pr_2301__0.19.0
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-github-pull-requests-board:pr_2301__0.15.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.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/github	1.48.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: 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

❌ Found 6 validation error(s):

File	Kind	Message
backstage-community-plugin-github-actions.yaml	mismatch	Version mismatch: expected "0.21.0" but got "0.18.0"
backstage-community-plugin-github-actions.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__0.21.0" but got "bs_1.45.3__0.18.0"
backstage-community-plugin-github-issues.yaml	mismatch	Version mismatch: expected "0.19.0" but got "0.16.0"
backstage-community-plugin-github-issues.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__0.19.0" but got "bs_1.45.3__0.16.0"
backstage-community-plugin-github-pull-requests-board.yaml	mismatch	Version mismatch: expected "0.15.0" but got "0.12.0"
backstage-community-plugin-github-pull-requests-board.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__0.15.0" but got "bs_1.45.3__0.12.0"