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
Hey! My team just started using gitpod. We are facing this issue: we open a ticket on Jira, and click on the linked Bitbucket PR. From there we expect to be able to start a workspace using the button added by the browser extension.
Problem is Gitpod hits us with a HTTPError: Not found.
Thanks for the report. Seems like we need to teach our contextURL resolver for bitbucket to deal with these UUIDs.
As it doesn't seem to be a blocker (a real annoyance, though!) I unfortunately can't give you a timeline for this atm as the team is busy with other developments
Bug description
Hey! My team just started using gitpod. We are facing this issue: we open a ticket on Jira, and click on the linked Bitbucket PR. From there we expect to be able to start a workspace using the button added by the browser extension.
Problem is Gitpod hits us with a
HTTPError: Not found
.This seems to happen because Jira changes the repo name in the URL to some sort of UUID. So instead of having this kind of URL: https://bitbucket.org/org-name/repo-name/pull-requests/XX, we have https://bitbucket.org/org-name/%7some-uuid%7D/pull-requests/XX.
If we manually replace the UUID by the repo name in the URL, reload the page and then click the button it all works fine.
Steps to reproduce
Workspace affected
No response
Expected behavior
I would expect Gitpod to be able to handle both URL types and open a workspace.
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: