backstage
CI/CD Actions Status (frontend) stopped working after version 1.24
Workspace
github-actions
📜 Description
When users select the CI/CD tab from the component "Home -> Select name -> CI/CD" the status is no longer working and instead the following message appears ...
"No Workflow Data This component has GitHub Actions enabled, but no data was found. Have you created any Workflows? Click the button below to create a new Workflow."
... but workflows were executed but they are no longer displayed.
It appears that this issue started with version 1.25 and we tried different releases up to 1.37
Here is what we found so far:
When a user tries to access CI/CD from the backstage component menu a new GitHub login call is made and a new temporary session key is created. The new session key is different than the existing session key and the permissions are not correctly assigned. That's why users can access the repo from the backstage component menu but can not access the CI/CD status.
It appears that the temporary GitHub auth token is treated differently starting at version 1.25 for front end “app” and back end “backend” operations.
👍 Expected behavior
Starting at version 1.25 the CI/CD status is no longer for existing Action workflows is no longer shown and the message ...
"No Workflow Data This component has GitHub Actions enabled, but no data was found. Have you created any Workflows? Click the button below to create a new Workflow."
... is shown instead.
👎 Actual Behavior with Screenshots
Starting at version 1.25 the CI/CD status is no longer for existing Action workflows is no longer shown and the message ...
"No Workflow Data This component has GitHub Actions enabled, but no data was found. Have you created any Workflows? Click the button below to create a new Workflow."
... is shown instead.
👟 Reproduction steps
📃 Provide the context for the Bug.
"dependencies": { "@backstage-community/plugin-github-actions": "^0.9.0", "@backstage/backend-common": "^0.24.0", "@backstage/catalog-client": "^1.6.6", "@backstage/plugin-kubernetes-backend": "^0.18.4", "@backstage/plugin-permission-common": "^0.8.1", "@backstage/plugin-proxy-backend": "^0.5.9", "@backstage/plugin-scaffolder-backend": "^1.26.3", "react": "^18.3.1", "react-dom": "^18.3.1" }
👀 Have you spent some time to check if this bug has been raised before?
- [x] I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- [x] I have read the Code of Conduct
Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else
Hi @offermannn, just wanted to note that this does work on the Demo site without any issue, example here: https://demo.backstage.io/catalog/default/component/backstage-demo/ci-cd. Code is here: https://github.com/backstage/demo. Maybe you could compare the setup?
Also, going from 1.25.0 to 1.38.0 is a year's worth of Backstage updates, there could be some manual changes that might be needed. Around 1.25.0 and 1.26.0 is when the new auth system came in.
Upon further investigation, we notice that the problem likely started from version 1.25, where the CI/CD tab no longer displays existing GitHub action workflows and instead shows the 'no workflow data ' despite the workflow being the successfully executed in the past
-
Was there any change in how the GitHub auth token / session is scoped or validated between frontend "app" and "backend " starting from v1.25? My observation it appears that the CI/CD status fails to load due to mismatch or limited scope of a temporary GitHub token
initiated during the CI/CD tab Access. -
Did the plugins interaction with GitHub APIs for fetching workflows change post v1.25? My observation if yes, could you clarify the expected auth context for these calls?
-
Are there any known permission-related regression introduced around GitHub session handling (eg-token lifetime, repo/workflow scope) in v1.25+? we are observing that while the repository is accessible, the workflow status is not suggesting a permission scope mismatch.
-
Is there work around to ensure consistent session key/token uses across frontend and backend for GitHub integration? My observation possibly a configuration suggestion for maintaining persistent tokes or syncing session behavior.
Hi @anushka-mckesson, thanks for the follow up, for clarity who is this directed to? Was it @offermannn or myself, or the community at large? That will just help me better understand the context and be able to follow up 👍
Hi @awanlin, Thanks for asking. This follow-up is really directed at the backstage plugin maintainers so you (@awanlin), (@offermannn) or anyone on the core team who can shed light on this. Of course, if other community members have insights, they are very welcome too.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @awanlin , Is there any solution for this? I'm also facing the same issue
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Alright, re-read all of this and I think step 1 is to to confirm is this still an issue for you @offermannn and @anushka-mckesson? If it is please upgrade to the latest Backstage version, ideally 1.43.0 but 1.42.0 would be fine as well. Once upgraded is the issue still present? If it is then please share exact steps to reproduce or a repo with the issue.
@shahrooqgunnu as you logged a separate issue I've replied to you there, please follow up on that issue instead 👍
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.