You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, in bitbucket server the project key is in repo url but in bitbucket cloud it is not.
bitbucket server : https://our-proxy.com/scm/PROJECT_KEY/our-repo.git
bitbucket cloud :https://bitbucket.org/our-team/our-repo.git
This means we must have repo names unique by team, is this by design?
Yes, it is.
Both are 2 different products, although Stash was renamed to Bitbucket Server to reflect the fact that the core functionality is the same. You can read more about that here but they both vary a lot in the features.
No, it isn't. The Workspace ID is in the URL, not the Project ID. The problem with this is the Workspace ID is global against every other customer using Bitbucket Cloud. Projects are used to group repos but the Project ID (for some insane reason) isn't a part of the repository URL.
It's a shame, when migrating from Bitbucket Server to the Bitbucket Cloud, you can't search the urls using the project key, also you can't create repos with the same name at the workspace level, in Bitbucket Server you can create repos with the same name and It does not affect it because the project key differentiates them.