|
|
Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
Page 2 of 3
| Bitbucket | GitHub | |
|---|---|---|
| Users | > 1 million | > 4 million |
| Projects | Aldrin, TortoiseHg... | Linux kernel, MongoDB, Neo4j, Couchbase, OpenShift... |
| Number of contributors | 0-5 | 6-10 | 11-25 | 26-50 | 51-100 | > 100 |
| Price | free | $10 | $25 | $50 | $100 | $200 |
| Number of repositories | 0-10 | 11-20 | 21-50 | 50-125 |
| Price | $25 | $50 | $100 | $200 |
The decision should be pretty straightforward. Here's a little calculator to figure out which one is right for you.
Project tracking integration
This is less a feature of Bitbucket or GitHub than of the project tracking software you use. It's worth mentioning, though,
because good integration is fantastic and timesaving. First look to see if your project management software integrates with
either. If it does, check out the features and weigh them against one another.
A basic integration would simply be linking changes to bugs or development tasks. Many project trackers go beyond that, providing luxury features (and after using these features, they do feel luxurious), like the ability to change the status of an issue or to log time to an issue from within a commit message.
We use Jira, which has support for both GitHub and Bitbucket, so that didn't narrow our search. If you use a different project tracking solution, do some research and see if it narrows yours.
Authentication
Nobody wants another set of login credentials, right? In the current climate, many apps will let you authenticate via your
OAuth2 provider of choice. Unfortunately, GitHub doesn't allow for external authentication. Each member of your team will
have to set up a new account at GitHub. Bitbucket, on the other hand, allows you to log in with Twitter, Google, Facebook,
OpenID, and GitHub (oh my!) credentials. This point isn't critical, but it's definitely worth considering.
| GitHub | OpenID | ||||
|---|---|---|---|---|---|
| Bitbucket | Yes | Yes | Yes | Yes | Yes |
| GitHub | Yes | No | No | No | No |
When we migrated to the cloud, one of our decision points for services was how you log in. In our case, we were adopting many new services and didn't want to deal with having to manage a ton of new credentials. Since we had already decided on Google for mail and other apps, we chose a set of services that met all of our needs and would allow for authentication via Google. This wasn't possible for every service we have, but I can log into most of them with a single account.
It's not a make-or-break feature, but single sign-on means fewer headaches for your developers, less time spent on lost password requests, and more productive hours.
User interface
This really comes down to two things: how aesthetically minded your developers are, and how often they will actually use the
Web interface. There are some tasks, like creating a remote repository, that are much easier to do in the Web GUI. Once that's
done, however, how much time will your developers spend in it? After you consider powerful CLI tools and IDE integration,
the Web UI looks more like a required convenience than anything else.