Need advice about which tool to choose?Ask the StackShare community!
Bitbucket vs Cloud9 IDE: What are the differences?
What is Bitbucket? One place to plan projects, collaborate on code, test and deploy, all with free private repositories. Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
What is Cloud9 IDE? Your development environment, in the cloud. Cloud9 provides a development environment in the cloud. Cloud9 enables developers to get started with coding immediately with pre-setup environments called workspaces, collaborate with their peers with collaborative coding features, and build web apps with features like live preview and browser compatibility testing. It supports more than 40 languages, with class A support for PHP, Ruby, Python, JavaScript/Node.js, and Go.
Bitbucket can be classified as a tool in the "Code Collaboration & Version Control" category, while Cloud9 IDE is grouped under "Cloud IDE".
Some of the features offered by Bitbucket are:
- Unlimited private repositories, charged per user
- Best-in-class Jira integration
- Built-in CI/CD
On the other hand, Cloud9 IDE provides the following key features:
- Real-time collaboration and chat
- Connect via SSH and FTP
- Code Completion (suggestions)
"Free private repos", "Simple setup" and "Nice ui and tools" are the key factors why developers consider Bitbucket; whereas "Easy to use", "Free" and "Nice UI" are the primary reasons why Cloud9 IDE is favored.
According to the StackShare community, Bitbucket has a broader approval, being mentioned in 1750 company stacks & 1493 developers stacks; compared to Cloud9 IDE, which is listed in 29 company stacks and 40 developer stacks.
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 repos904
- Simple setup398
- Nice ui and tools346
- Unlimited private repositories341
- Affordable git hosting240
- Integrates with many apis and services123
- Reliable uptime119
- Nice gui86
- Pull requests and code reviews84
- Very customisable58
- Mercurial repositories16
- SourceTree integration14
- JIRA integration11
- Track every commit to an issue in JIRA10
- Deployment hooks8
- Best free alternative to Github8
- Automatically share repositories with all your teammates7
- Compatible with Mac and Windows7
- Source Code Insight6
- Create a wiki5
- Login with Google5
- Price5
- Approve pull request button5
- #2 Atlassian Product after JIRA4
- Customizable pipelines4
- Continuous Integration and Delivery3
- Unlimited Private Repos at no cost3
- Also supports Mercurial3
- Academic license program2
- Mercurial Support2
- IAM2
- Issues tracker2
- Open source friendly2
- Teamcity2
- Multilingual interface2
- IAM integration2
- Free Private Repositories0
Pros of Cloud9 IDE
- Easy to use107
- Free101
- Nice UI76
- Terminal access to vm instead of simulation65
- New full ubuntu machines58
- Easy dev environment49
- Ssh access to your own machine44
- Real-time with other people43
- Free prototype hosting43
- Collaboration32
- Open Source10
- Great syntax highlighting6
- Works great5
- Nice ide4
- Better IDE than the others4
- Extremely easy setup4
- Great interface, download or upload file is nice.4
- Its easy to share code3
- You can run your project easier3
- Open-source friendly3
- Good documentation2
- Bitbucket integration1
- Versatile and robust1
- Need a credit card to get access1
- Starts a VM1
- Easy to use, seem fast, friendly ui1
- Good0
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 buggy14
- 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
Cons of Cloud9 IDE
- Not free4