Bitbucket Server Reviews

It shows any contact records at the backend. But, if we face any config guard, any filing data, or any formatting error, then we can easily monitor in the Bitbucket pipeline itself. If a specific branch of code has an error, we have to look into that particular branch instead of looking into the overall code, and overall backup.

If I want to mail someone a master branch, then sometimes it shows some conflict with other codes in the master branch.

When we clear that master branch, clear those lines, resolve them, and try to push again, it shows the conflict error. It's some kind of server issue or it's some kind of different particular brand issue. When we try to push the specified code, instead of that, sometimes it automatically saves all local files, which are available in the particular branch. 

Then we get a server issue. When we are faced with this problem, we need to remove that particular branch, and we once again, create the new branch, and once again, pull the changes around.

I have been using Bitbucket Server for two years. 

The solution is easily scalable.

The initial setup is straightforward. It takes half an hour to deploy. 

Overall, I rate the solution a seven out of ten. 

The permission system for Git repositories and viewing all contributions to a Git repo are the most valuable features I could think of. In addition, it is really nice that users can create their personal repositories.

Stash really helped us to introduce a very granular permission system for our software repositories. Furthermore it makes working with Git a lot easier since users can manage most things with a decent Web GUI.

It is a Java application and runs its own SSH server, and that means that there is a certain overhead on your system. Besides that, Stash really does what it should do.

I have been using this solution for about a year.

No issues encountered.

No, although we have a lot of code stored inside our repositories.

Although we have a huge amount of Git repositories inside Stash, we haven't encountered any scalability issues.

We haven't contacted customer service, so I can't really say how good they are.

We haven't contacted technical support either.

We used Crucible and Fisheye from the same vendor and linked it to our existing SVN and Git servers. We switched because a normal Git installation doesn't provide a permission system.

Everything was straightforward. Atlassian ships Stash with a decent installation wizard.

We implemented it ourselves.

To be honest, I didn't find any solution which did exactly what we needed (besides BitBucket Server).