HN user
Product Manager at Atlassian
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.
Bitbucket PM here, sorry to hear this doesn't suit you. Could you tell me more? If like to better understand your concern.
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.
I am a Bitbucket product manager.
There are a few options for configuration management and automation.
The installer[1], web setup[2] and almost everything in settings/admin/provisioning can be done via a config file, script or REST call[3].
There are a few 3rd party modules for config management tools available that make use of this:
Chef: https://github.com/bflad/chef-stash
Puppet: https://forge.puppetlabs.com/thewired/Bitbucket
We also provide a docker image that may be of interest: https://hub.docker.com/r/atlassian/bitbucket-server/
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.
[1] https://confluence.atlassian.com/bitbucketserver/running-the...
[2] https://confluence.atlassian.com/bitbucketserver/automated-s...
[3] https://developer.atlassian.com/bitbucket/server/docs/latest...
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?
Thanks, very nice of you to say! We like that kind of feedback too :)
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 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.
Disclosure: I work for Atlassian
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.
https://www.atlassian.com/software/stash
Disclosure: I work for Atlassian