-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
1
-
Problem Definition
While the Cloud and Server/DC products have significant differences, it would be good to unify the approach two applications are building URL to allow the 3rd party tools to use unified URL mask for both Bitbucket Cloud and Server DC.
As example, Bitbucket Server is hosting raw content with these URLs:
https://<server>/users/<user>/repos/<repo>/raw/<file>?at=552de4276227d4caa4b7bac3f3889d3194388fc2
https://<server>/projects/<project>/repos/<repo>/raw/<file>?at=<commit>
https://<server>/rest/api/1.0/projects/<project>/repos/<repo>/raw/<file>?at=<commit>
While in Bitbucket Cloud raw content is exposed as this:
https://bitbucket.org/<user>/<repo>/raw/69ab3ba74e87e3967816b0f0088c6912b332f65b/<path>/<file>
Suggested Solution
It would be good to switch to a unified way to simplify the usage of 3rd party integrations with both Cloud and Server installation.