Assembla provides a cloud-based source code management (SCM) Platform that covers Perforce, Apache Subversion (SVN), and Git. Their managed cloud hosting solutions are designed for both small and enterprise software development teams. They offer a turn-key cloud hosting solution that covers both Perforce and infrastructure management. This includes design and managed dedicated server network. And Assembla's Subversion Enterprise offers Assembla Cloud features on a dedicated, high-performance…
$19
per month per user
Bitbucket Server (discontinued)
Score 6.0 out of 10
N/A
Bitbucket Server (formerly Stash) from Atlassian was a self-hosted source code management solution. The product is no longer available for sale, and support for existing licenses ended in 2024.
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.
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.
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)
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.
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.
Assembla was actually chosen by our vendor so we did not have a say in the selection. However, the product more than served the need we had for better distribution and completion of tasks. It has an easy to view interface, user friendly and efficient. I would recommend it to anyone who is looking for a way to manage ongoing projects.
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.
We were able to spend less time tracking down the status of projects.
We could become more self-sufficient on reviewing prior resolutions to help with current problems.
Tasks were responded to quickly because we did not have to email one person, wait for an out of office email and then try someone else. Our task got assigned to the next available person.
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.
