I'm a Bitbucket Product Manager. Thanks for the feedback! This is an area we plan to improve in the Server offering. In particular we're actively looking at ways to make diff nav and find much better.
Sure! We don't have any NFS infrastructure, so migrating to BitBucket means paying for the license + some kind of SAN + engineers to look after it.
We'd much prefer to use EFS but I understand that it's not supported, since there's no way to set `lookupcache=positive` (git push might update the ref to an object which may not be immediately available across all NFS clients & they would cache that the object doesn't exist unless this is set)[0]
I think they just announced that AWS is a first class supported platform (I'm here at their conference) so it might be worth looking again. Of course that might be Data Center products only so don't quote me on it. I'm sure someone from Atlassian is around here and can confirm.
It sounds like you might also (or rather) be looking to do things by groups people (ie self-organised teams), rather than a multi-level repository structure?
I'm a product manager at Atlassian, feel free to email me (rbarnes@) if you'd like to crack this open, I'd love to hear more.
You're right about commit notification emails, an add-on is currently the best way to get this. It's something we'd love to add soon but isn't being worked on right now. You can hook up HipChat notifications for new commits as an alternative, and one that means less email.
As for clustering, Bitbucket Data Center[4] provides the same self-hosted functionality as Bitbucket Server for 500+ user tiers, with active-active clustering for performance at scale and HA, as well as Smart Mirroring for distributed git read performance.
Feel free to email me (rbarnes@) if you have feedback on how these options work for you.
I'm a product manager for Stash, and was curious about your expected Stash/JIRA workflow. Why would a reviewer be assigned to the JIRA ticket? They're assigned to the pull request for the issue that the author is assigned to (who did the work). Are you wanting to have a JIRA-only view of work that needs doing, including review?
I'm a product manager for Stash. I'd love to know more about what you find lacking in Stash. We've got a bumper crop of improvements in the works that we think are useful, but the more feedback to guide us, the better.
Stash, in my opinion, is the best git tool out there. Sadly it's sometimes tough to convince people to switch when Github is 'good enough'. Anyway, keep up the good work!
Stash has a number of integration points where similar checks could be applied, the most similar to GitCop being a merge check. That said, a pre-receive hook would make a lot more sense.
Atlassian Stash provides self-hosted git repository management that provides code review, and is getting better with every release. It is based on the concept of pull requests also but provides workflow better suited to teams, including the ability to require successful builds and reviewer approvals. In addition it has awesome diff views and a plugin architecture for customising behaviour and integrating with other development tooling.
