harness / harness/backstage-plugins

[Bug]: Integration with backstage isn't reflecting/displaying in backstage application

Open
#104 28 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
39
Forks
30
PR merge metrics
No merged PRs in 30d

Description

Expected Behavior

CI/CD tab should render harness pipeline details.

Actual behavior

CI/CD tab isn't reflecting any harness pipeline details and still asking to add relevant annotations.

Context

We followed all the steps mentioned in readme to integrate the harness CI/CD into Backstage but it's not reflecting in Backstage i.e. we don't see the pipeline details in the component's CI/CD tab when we launch Backstage application. We don't see any errors in console and we have used harness cloud platform with free license.

Environment details

Our current backstage versions:

Node: v18.18.0
Yarn: v1.22.19
@backstage/catalog-client @ ^1.4.6 bumped from 1.4.6 to 1.5.0
@backstage/core-components @ ^0.13.8 bumped from 0.13.8 to 0.13.9
@backstage/core-plugin-api @ ^1.8.0 bumped from 1.8.0 to 1.8.1
@backstage/integration-react @ ^1.1.21 bumped from 1.1.21 to 1.1.22
@backstage/integration @ ^1.7.2 bumped from 1.7.2 to 1.8.0
@backstage/plugin-catalog-common @ ^1.0.18 bumped from 1.0.18 to 1.0.19
@backstage/plugin-catalog-react @ ^1.9.1 bumped from 1.9.1 to 1.9.2
@backstage/plugin-permission-common @ ^0.7.10 bumped from 0.7.10 to 0.7.11
@backstage/plugin-permission-react @ ^0.4.17 bumped from 0.4.17 to 0.4.18
@backstage/plugin-search-common @ ^1.2.8 bumped from 1.2.8 to 1.2.9
@backstage/core-components @ ^0.11.1 should be changed to ^0.13.9
@backstage/frontend-plugin-api @ ^0.3.0 should be changed to ^0.4.0
@backstage/theme @ ^0.2.16 should be changed to ^0.5.0
@backstage/theme @ ^0.4.4 should be changed to ^0.5.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Harness CI/CD integration using the README steps and the listed Backstage and Harness environment details. Inspect why the CI/CD tab still requests annotations despite the integration setup; done when the component displays its Harness pipeline details without console errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.