Update argocd workspace to commit e53ced9 for backstage 1.49.2 on branch main

[github-actions]

Update argocd workspace at commit backstage/community-plugins@e53ced9 for backstage 1.49.2 on branch main.

This PR was created automatically.

🎉 Override Can Be Removed!
The overlay currently contained an override at workspaces/argocd/backstage.json. This upgrade is an Exact Match for Backstage 1.49.2,, so the override shoudld be removed.
Click on the following link to see the source diff it introduces: backstage/community-plugins@f226813...e53ced9.

Before merging, you need to export the workspace dynamic plugins as OCI images,
and if possible test them inside a RHDH instance.

To do so, you can use the /publish instruction in a PR review comment.
This will start a PR check workflow to:

• export the workspace plugins as dynamic plugins,
• publish them as OCI images
• push the oci-images in the GitHub container registry with a PR-specific tag.

[openshift-ci]

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.6.0
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.1.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.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/argocd	1.47.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

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

[openshift-ci]

@github-actions[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.6.0
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.1.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.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/argocd	1.47.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

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dzemanov]

We can update ArgoCD to 1.48 to get rid of the Backstage incompatible workspaces message, as it was already updated to that version here: backstage/community-plugins#8115

[dzemanov]

/publish

[github-actions]

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.7.1
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.2.1

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.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/argocd	1.48.5	⚪	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

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

[openshift-ci]

@github-actions[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.7.1
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.2.1

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.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/argocd	1.48.5	⚪	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

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

A new workspace commit 1db8b1ce09230e2bb57a0865c9e25116305fe534 has been discovered (match type: 'best-effort').
You can update this PR with the latest discovered workspace source commit.

To do so, you can use the /update-commit instruction in a PR review comment.

[github-actions]

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.7.1
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.2.1

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.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/argocd	1.48.5	⚪	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

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

[openshift-ci]

@github-actions[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.7.1
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.2.1

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.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/argocd	1.48.5	⚪	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

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dzemanov]

/publish

[github-actions]

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.7.1
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.2.1

Backstage Compatibility Check

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

No action required.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

[openshift-ci]

@github-actions[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.7.1
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.2.1

Backstage Compatibility Check

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

No action required.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dzemanov]

/publish

[github-actions]

✅ Smoke tests workflow passed. All plugins loaded successfully.

[github-actions]

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.7.1
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.2.1

Backstage Compatibility Check

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

No action required.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

[openshift-ci]

@github-actions[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.7.1
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.2.1

Backstage Compatibility Check

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

No action required.

Metadata Validation

✅ All metadata files validated successfully.

Running e2e tests
/test e2e-ocp-helm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

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

[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-argocd:pr_2151__2.6.0
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.1.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/argocd	1.47.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 2 validation error(s):

File	Kind	Message
backstage-community-plugin-argocd-backend.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__1.1.0" but got "bs_1.48.3__1.1.0"
backstage-community-plugin-argocd.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__2.6.0" but got "bs_1.48.3__2.6.0"

[github-actions]

A new workspace commit 21b9c09f91899ccaf2117804e1e6c2be2b087b9f has been discovered (match type: 'exact').
You can update this PR with the latest discovered workspace source commit.

To do so, you can use the /update-commit instruction in a PR review comment.

[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-argocd:pr_2151__2.6.0
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.1.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/argocd	1.47.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 2 validation error(s):

File	Kind	Message
backstage-community-plugin-argocd-backend.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__1.1.0" but got "bs_1.48.3__1.1.0"
backstage-community-plugin-argocd.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__2.6.0" but got "bs_1.48.3__2.6.0"

[PatAKnight]

/update-commit

[github-actions]

Publish workflow has completed with failure.

[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

[github-actions]

Publish workflow has completed with failure.

[github-actions]

Publish workflow has completed with failure.

[github-actions]

Update Commit workflow has completed with failure.

[github-actions]

Publish workflow has completed with failure.

[github-actions]

Publish workflow has completed with failure.

[github-actions]

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.8.0
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.4.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]

✅ Smoke tests workflow passed. All plugins loaded successfully.

[rhdh-test-bot]

✅ Passed E2E Tests - argocd

Platform: ocp 4.18 | RHDH Version: 1.10 | Duration: 9m 43s
Passed: 7 | Failed: 0 | Flaky: 0 | Skipped: 0
Playwright Report | Build Log | Artifacts

[davidfestal]

/update-commit

[github-actions]

Update Commit workflow has completed with failure.

[github-actions]

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.8.0
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.4.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]

✅ Smoke tests workflow passed. All plugins loaded successfully.

[rhdh-test-bot]

❌ Failed E2E Tests - argocd

Platform: ocp 4.18 | RHDH Version: 1.10 | Duration: 2m 8s
Passed: 0 | Failed: 1 | Flaky: 0 | Skipped: 6
Playwright Report | Build Log | Artifacts

[davidfestal]

/update-commit

[github-actions]

Update Commit workflow has completed with success.

[github-actions]

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd:pr_2151__2.8.0
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-argocd-backend:pr_2151__1.4.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]

✅ Smoke tests workflow passed. All plugins loaded successfully.

[rhdh-test-bot]

✅ Passed E2E Tests - argocd

Platform: ocp 4.18 | RHDH Version: 1.10 | Duration: 9m 24s
Passed: 7 | Failed: 0 | Flaky: 0 | Skipped: 0
Playwright Report | Build Log | Artifacts