-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Integration with backstage isn't reflecting/displaying in backstage application #104
Comments
Hi Anuj, can you please share the |
We tried both old and new annotations with two components. Sharing the catalog-info.yaml for both the components. apiVersion: backstage.io/v1alpha1 apiVersion: backstage.io/v1alpha1 |
@rakeshkumarltim You seem to have added the annotations under the https://github.com/harness/backstage-plugins/blob/main/examples/catalog-harness-cicd-new.yaml |
Thank you OrkoHunter. I have updated the my catalog-info.yaml and now I could see the dropdown in my CI/CD tab. But execution details are not listed, instead getting a message "Could not find the pipeline executions, please check your configurations in catalog-info.yaml or check your permissions.". Can you help me to fix this? apiVersion: backstage.io/v1alpha1 |
@rakeshkumarltim - The log you have attached says there are two different pipelineIdentifier. Ideally, there should be only one pipelineIdentifier. Could you check the log once? Did CI/CD work for the other component with old annotation? |
@rakeshkumarltim - We can also check if the generated X-Api-key has necessary permission to view pipeline executions. curl --location 'https://app.harness.io/gateway/pipeline/api/pipelines/execution/v2/summary?accountIdentifier={ACCOUNT_ID}&routingId={ACCOUNT_ID}&projectIdentifier=default_project&orgIdentifier=default&page=0&size=5&pipelineIdentifier={PIPELINE_ID}' |
@vigneswara-propelo : Output of the curl command is , "status":"ERROR","code":"INVALID_TOKEN","message":"Token is not valid.","correlationId":null,"detailedMessage":null,"responseMessages":[{"code":"INVALID_TOKEN","level":"ERROR","message":"Token is not valid.","exception":null,"failureTypes":[]}],"metadata":null}--header: command not found Tried to use both pat (pat.xxxx.xxxx) & sat (sat.xxxx.xxxx) token and result is same. And the token is valid still |
I guess you are trying this curl in your terminal and not in postman. curl --location 'https://app.harness.io/gateway/pipeline/api/pipelines/execution/v2/summary?accountIdentifier={ACCOUNT_ID}&routingId={ACCOUNT_ID}&projectIdentifier=default_project&orgIdentifier=default&page=0&size=5&pipelineIdentifier={PIPELINE_ID}' --header 'content-type: application/json' --header 'x-api-key: {X-API-Key}' --data 'null' |
@vigneswara- thanks for your suggestion, tried and following is a brief snapshot of the output, please let us know if you need any other info -
|
@anuj-ltim Can you share the proxy config you have defined in app-config.yaml? |
@jenil-harness kindly refer below -
|
@anuj-ltim Config should be 'harness/prod':
target: 'https://app.harness.io/'
headers:
'x-api-key': pat.xxx.xxx |
@jenil-harness thanks for the suggestion. I did update like you suggested, don't see any errors in console but still pipeline isn't displayed. Thanks for trying to help us out, truly appreciate it.
|
@anuj-ltim Inspect -> Network -> Filter by /harness/prod. |
@jenil-harness does the below snapshots help or need anything I can help with ? |
Hi @anuj-ltim looking at your API calls, it's clear that there's some issue with your annotations in the |
We are facing the same issue as well. We are able to produce the dropdown of Service / Pipelines specified in the label but then we get the same error that @rakeshkumarltim described. I have tried different variations of the pipeline URL with no luck.
|
Hi @michael-pang could you please update the URL to be of this format |
@Debanitrkl where do we specify the pipeline ID in these URLs? How does it know what pipeline to populate? Also if that is the case then the images in the documentation are not clear. |
@michael-pang the way this plugins works is it will fetch data for the recent pipeline executions in your project. |
For pipelines, when you're using |
Here's the example mentioned in the documentation |
@Debanitrkl same issue unfortunately. If I leave
If I remove |
Please try to with the URL format that I provided here #104 (comment): |
@Debanitrkl I have tried keeping it with |
Could you please share the |
Here is the I am getting the following error in Backstage: |
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:
The text was updated successfully, but these errors were encountered: