Beanstalk vs. Bitbucket Server (discontinued)

For business or personal applications, where you wish your code to remain private and/or proprietary, Beanstalk could be a good fit. If you are also interested in beginning to automate with relative ease, their tools can be a great help. Code reviews can also be a key factor in the decision, as they provide a good framework for accountability.

Incentivized

Bitbucket Server (formerly Stash) is suitable for departments or teams with the capacity to manage and support their own products and the availability to implement the tool on their own infrastructure. Bitbucket Server (formerly Stash) enables a good framework based on git to integrate the development cycle and to handle anything from a minor group of users and repositories to an extended usage with multiple users and roles collaborating in different projects.

Incentivized

• Automation
• Code Review
• Support

Incentivized

• Projects & Permissions - Stash keeps you and your developers productive by providing a way to structure your repositories and manage permissions via a simple, yet powerful user interface. Stash is very easy to use, manage & administer.
• Essentially Stash gives two versions of interfaces to work with.
• Stash Repository hosted on a server.
• Atlassian SourceTree.
• Atlassian Sourcetree is a tool to work with a code in stash. The two 'web' and 'desktop' versions make working with code user friendly, intuitive and comprehensive.
• Connectivity to JIRA - Stash keeps track of all issues associated with commits. Users can use Stash to quickly see all issues associated with a commit, or use the Source tab on JIRA issues for an aggregate view of all the code changes that are related to a specific JIRA issue. With this information available, your development team saves time when tracking particular bug fixes or improvements.

Incentivized

• Interface is not always intuitive, some areas are easier than others to navigate.
• Price plans are a little odd. However, they do seem to be flexible if a plan does not quite fit your needs.

Incentivized

• You can't allow users to create new repositories without them being full admins of a whole project
• There's not a way to limit who can merge a pull request (e.g. allow only the author to merge) outside of branch permissions
• Some settings like default reviewers can't be easily copied to different repositories (without setting default reviewers at the project level, which we don't want to do because a single project has multiple team's code under it)

Incentivized

Because we're so locked in, it's likely we'll be using Bitbucket Server for a while, unfortunately.

Incentivized

The usability of its interface is pretty straight forward when it comes to creating projects and repositories, but when you have to dive into finer grained portions of the UI things can get tricky. If you are used to using tools like GitHub or Gitlab -- Bitbucket is just different enough to be a bother.

Incentivized

Never really needed any support as the application is very easy to set up and maintain. Any questions we had were well documented in their online documentation, and community forum.

Incentivized

If you are creating open source applications, there is almost no reason not to use GitHub. If you do need private repositories (for proprietary or private, business or personal use), Bitbucket could be an excellent solution. Beanstalk's main advantages lie in the support (which is excellent), deployment tools, and code review features.

Incentivized

We migrated several of our applications to BitBucket from legacy Team Foundation Server, and the experience has been significantly better. It's easy to use and plenty flexible. Other solutions such as GitHub are also good, but we needed to keep everything on-prem due to constraints around our industry and company, though we are currently re-evaluating whether we can move to something cloud based in the future.

Incentivized

• Increased automation => better accuracy and efficiency of maintenance/launches
• Better insights into ongoing work and past modifications to code => lower chance of error and more efficient troubleshooting

Incentivized

• In positive form, having Stash over not having it at all has provided us with a superior repository system over trying to push to some local server instance and manage branches/merging from our local machines.
• There are no real negatives to using Stash, its only problem is that there are competitors out there that can offer additional features.

Incentivized