Need advice about which tool to choose?Ask the StackShare community!
Bitbucket vs Phabricator: What are the differences?
## Introduction
Here are the key differences between Bitbucket and Phabricator:
1. **Integration**: Bitbucket integrates seamlessly with Jira, allowing for easy management of issues, agile boards, and workflows together. Phabricator, on the other hand, offers integration with a wide range of tools but may require some configuration for seamless synchronization.
2. **Code Review Process**: Bitbucket provides a simple and straightforward code review process with the use of pull requests. Phabricator offers a more advanced and customizable code review process with features like Herald rules, which automate specific actions based on certain conditions.
3. **Workflow Customization**: Bitbucket's workflow customization capabilities are limited compared to Phabricator, which allows extensive customization through the use of Maniphest, allowing teams to create custom workflows tailored to their specific needs.
4. **Continuous Integration**: Bitbucket offers native integration with Bitbucket Pipelines for continuous integration and delivery (CI/CD) pipelines. Phabricator requires the use of external tools like Jenkins for setting up CI/CD pipelines.
5. **Documentation**: Bitbucket provides basic documentation features such as wikis and README files within repositories. Phabricator offers a more comprehensive documentation engine called Phriction, which allows for rich text editing and the creation of detailed documentation pages.
6. **Permissions and Access Control**: Bitbucket has a more straightforward permission and access control system, allowing for easy management of user roles and permissions. Phabricator offers a more granular control system with the use of audit and authentication policies for added security and compliance.
In Summary, the key differences between Bitbucket and Phabricator lie in integration capabilities, code review processes, workflow customization, continuous integration tools, documentation features, and permissions/access control systems.
I first used BitBucket because it had private repo's, and it didn't disappoint me. Also with the smooth integration of Jira, the decision to use BitBucket as a full application maintenance service was as easy as 1, 2, 3.
I honestly love BitBucket, by the looks, by the UI, and the smooth integration with Tower.
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 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
Pros of Phabricator
- Open Source33
- Code Review29
- Supports Git/Hg/SVN25
- Bug Tracking18
- Audit Source Code17
- Unlimited Repo Support11
- Software Engineering Platform10
- Super fast task creation10
- Flexible Project Management9
- Project Management8
- Self hosted5
- Building Better Software4
- Best Integration with Gitlab2
- Complete set for collaborating on software development2
- Powerful, Complete, Fast, Reliable and Open Source1
- Straightforward code review process1
- Workflow1
- Very effective system, does all PM & code org needed1
Sign up to add or upvote prosMake informed product decisions
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