Need advice about which tool to choose?Ask the StackShare community!
Atlassian Stash vs Bitbucket: What are the differences?
Introduction:
Atlassian Stash and Bitbucket are both version control repositories that are widely used in software development projects. They offer similar functionalities but have several key differences that set them apart.
Hosting options: One of the key differences between Atlassian Stash and Bitbucket is the hosting options they offer. Stash can only be hosted on-premises, meaning it requires a dedicated server within the organization's infrastructure. On the other hand, Bitbucket offers both on-premises and cloud-based hosting options, providing more flexibility for users.
Scalability: Scalability is another significant difference between Stash and Bitbucket. Stash is known for its limited scalability as it relies on the hardware resources available on the on-premises server. In contrast, Bitbucket is designed to scale effortlessly in the cloud, allowing teams to handle increasing workloads and accommodate rapid growth.
Integration with Atlassian products: As both Stash and Bitbucket are developed by Atlassian, they integrate seamlessly with other Atlassian products. However, Bitbucket offers deeper integrations with a broader range of Atlassian tools, such as Jira, Bamboo, and Confluence. This integration allows for better visibility, collaboration, and traceability across the development lifecycle.
Pricing models: Pricing is an essential consideration for organizations when choosing between Stash and Bitbucket. Stash follows a traditional perpetual licensing model, where users pay upfront for the software licenses. In contrast, Bitbucket has a subscription-based pricing model, which allows users to pay on a monthly or yearly basis. This difference in pricing models allows organizations to choose the option that suits their budget and scalability requirements.
Code review capabilities: Both Stash and Bitbucket offer code review functionality, but there are some differences in their approach. Stash provides a more traditional code review process, where reviewers need to approve or reject changesets. Bitbucket, on the other hand, offers a more collaborative and flexible code review process, allowing reviewers to provide inline comments and suggestions directly on the code.
Third-party integrations: While both Stash and Bitbucket support integrations with various third-party tools, Bitbucket has a more extensive ecosystem of integrations. Bitbucket Marketplace offers a wide range of plugins and extensions that users can utilize to enhance their development workflow. Stash, although it supports some third-party integrations, has a more limited selection.
In summary, the key differences between Atlassian Stash and Bitbucket lie in hosting options, scalability, integration with Atlassian products, pricing models, code review capabilities, and third-party integrations. Bitbucket offers more flexibility, scalability, and extensive integrations, making it a preferred choice for many organizations.
Do you review your Pull/Merge Request before assigning Reviewers?
If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:
- Pick the correct target branch
- Make Drafts explicit
- Name things properly
- Ask help for tools
- Remove the noise
- Fetch necessary data
- Understand Mergeability
- Pass the message
- Add screenshots
- Be found in the future
- Comment inline in your changes
Read the blog post for more detailed explanation for each item :D
What else do you review before asking for code review?
One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i
is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.
It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.
Pros of Atlassian Stash
Pros of Bitbucket
- Free private repos905
- Simple setup397
- Nice ui and tools349
- Unlimited private repositories342
- Affordable git hosting240
- Integrates with many apis and services123
- Reliable uptime119
- Nice gui87
- Pull requests and code reviews85
- Very customisable58
- Mercurial repositories16
- SourceTree integration14
- JIRA integration12
- Track every commit to an issue in JIRA10
- Deployment hooks8
- Best free alternative to Github8
- Automatically share repositories with all your teammates7
- Source Code Insight7
- Compatible with Mac and Windows7
- Price6
- Login with Google5
- Create a wiki5
- Approve pull request button5
- Customizable pipelines4
- #2 Atlassian Product after JIRA4
- Unlimited Private Repos at no cost3
- Also supports Mercurial3
- Continuous Integration and Delivery3
- Mercurial Support2
- Multilingual interface2
- Teamcity2
- Open source friendly2
- Issues tracker2
- IAM2
- Academic license program2
- IAM integration2
Sign up to add or upvote prosMake informed product decisions
Cons of Atlassian Stash
Cons of Bitbucket
- Not much community activity19
- Difficult to review prs because of confusing ui17
- Quite buggy15
- Managed by enterprise Java company10
- CI tool is not free of charge8
- Complexity with rights management7
- Only 5 collaborators for private repos6
- Slow performance4
- No AWS Codepipelines integration2
- No more Mercurial repositories1
- No server side git-hook support1