You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then, it just shows the report in iframe as follofwing:
But when I try this link directly in browser, then I get 404
Without index.html it's Ok.
The allure-docker-service was deployed in k8s using your manifest files (with edits). But when I try the URL directly with port-forward to allure-docker-service-ui:5252 then it behaves the same. It returns 404 if I add index.html in the end, so, it's not an issue of ingress.
The text was updated successfully, but these errors were encountered:
Hi Frank,
Thank you for the great tool. But I’d appreciate your help.
I use Allure Plugin for Backstage.
It generates the ReportUrl as the following.
The same in the repo:
https://github.com/backstage/community-plugins/blame/013521a1d31bfea0f001708d4afcc940af6dc9ea/workspaces/allure/plugins/allure/src/api/AllureApiClient.ts#L28
(i.e. with index.html in the end)
Then, it just shows the report in iframe as follofwing:
But when I try this link directly in browser, then I get 404
Without index.html it's Ok.
The allure-docker-service was deployed in k8s using your manifest files (with edits). But when I try the URL directly with port-forward to allure-docker-service-ui:5252 then it behaves the same. It returns 404 if I add index.html in the end, so, it's not an issue of ingress.
The text was updated successfully, but these errors were encountered: