Also, the degree to which Atlassian products integrate varies a lot. FishEye and Crucible integrate closely. Both of them integrate OK with Jira. Neither of them really integrate at all with Stash, which has its own implementation of code browsing, search, and review. Jira and Stash integrate acceptably, but not very flexibly, and not to a level that surpasses any number of third-party integrations.
And there's no level of integration that would make Confluence worth using.
There is no good reason to be a full-boat Atlassian shop, period. If Jira is what you want, use it; I'm not a huge fan of it conceptually but it there's nothing wrong with it. Crucible is decent if you're willing to put the effort in to get it set up for your workflow. Nothing else of theirs I've used is worth the time it takes to set up, let alone the cost.
CEO of Atlassian here. Can you list the features you deem missing? I want to check them against our roadmap, as I don't believe we have many gaps, and a host of things better.
Here's some additional things off the top of my head...
- search! maybe our fisheye isnt indexing all our repos properly (we just recently migrated 10+ years of svn codebases too, in addition to a slew of new git repos) but I would have hoped to be able to do deep code searches within stash itself, across many/all repos.
- project areas: Only one level hierarchy. we'd rather be able to form adhoc groups (think github organizations) under those project areas
cant think of any more right now but it's late saturday evening :) but you can certainly have your folks contact us at CBP and we'd be happy to give deeper feedback if you want it
Search is known and being worked on. FishEye should work in the interim until we do Stash native search - if not - please contact our support team.
Project areas - will get the team to dig into this more, and understand the real underlying use-case you need this. Is it search? Permissions? Discovery?
Stash and Bitbucket have converged more than I expected, mostly because my recollection of Bitbucket was closer to Github than it actually is. But versus Bitbucket, Stash is missing Mercurial support, snippets, issues, wiki, project overview pages, and some social features. The lack of snippets was particularly vexing to me in my day-to-day work until we started using Slack. And Slack snippets are still a poor substitute for Gists.
Versus Github, the difference is more pronounced. Github has better search (and it isn't even that good), much nicer pull requests with superior integration to the issue tracking system, a much better API, better profile pages, static site generation, and in-place editing.
Yes, I know the answer to the lack of some of those features is "use our other products too", but Atlassian's competitors offer products with lightweight issue tracking and wikis. And while the features Stash provides are generally decently implemented and usable (the last few versions have been a big improvement), Confluence... is poorly suited to be used as a programmers' wiki, to use the gentlest language I can muster.
Using this for work:
- Would love to be able to see something on my profile page. I've got hundreds of commits but my user page is completely empty. Maybe this is because our repos are private, but since I'm logged in I would expect to see something.
- I love GitHubs personal commits page, as well as the reporting features baked into each repo. I think it would make the higher ups happy if they could see how active we are.
Note that there is a plugin that seems to do this, but while it's cheap for 10 users the price escalates at a weird rate ($1 to $6 to $8 /user at the first three tiers). At this point I'm hoping we can trial it out to show how much it would help with reporting/at a glance metrics, and then hopefully find funds for it. Or find a package to generate these locally. I'm not sure why this isn't just baked in though.
- Triggering emails when commits are made seems to be a plugin? Or email isn't setup correctly yet. This one still needs to be dug into.
- This is a value add: README file support for projects?
Maybe it's intentional, but coming from GitHub a local server install of Bitbucket is just so plain.
Edit: And kudos for reading Hacker News and leaving a comment asking for feedback.
Email should be built in. Raise a support ticket with our amazing support team if any issues with that.
I'll check on README. I thought we had equivalent, but perhaps in a different place. Will have to wait until the team wakes up.
> Maybe it's intentional, but coming from GitHub a local server install of Bitbucket is just so plain
We try to be deliberate about adding features that matter. The Bitbucket server team is one of the best at Atlassian, so hopefully you're saying the lack of "right features" is the issue, not just the extra whitespace.
Thanks for taking time to add feedback. I really appreciate it & helps us make a better product.
Never tried it without the .md extension since that was the Github default (IIRC).
Could you make it so that you could just lay down files, attach storage and start the service?
Also, clustering (active/active) word be awesome.
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...
For Clustering - any reason you need active/active? We have mirroring[1] which (from our chats with most of our customers) is what people prefer.
[1] - https://confluence.atlassian.com/bitbucketserver/smart-mirro...
Please use the same markdown syntax across ALL your products.
No excuse, but wanted to set expectations.
