The Bitbucket Blog is the Git hosting service's product blog, covering features, outages, security and releases.
Commenters praise Bitbucket's branch restrictions and free private repos, and link its downtime post-mortem as a warning about TCP syslog.
Mr..Mrs. Cookie! I love Ice.... In my drinks but not for Bitbucket.
Bitbucket has released some pretty major stuff in just the last 6 months or so. Built in Pipelines are an example. We've got some other stuff coming soon and there is always more in the pipeline after that.
https://news.ycombinator.com/item?id=11759733
Bitbucket added support for large files and went a step beyond GitHub and Gitlab by adding file chunking to speed things up in a big way. Bitbucket added file previews to help those working with large files like gaming devs. Smart mirroring to helps remote devs work faster. I could go on but I don't want to spam this thread with a feature list.
There's a nice little post here with some things. https://blog.bitbucket.org/page/2/
Do you use Trello instead of JIRA? If so, awesome! It is a great product. We love it so much we spent around a full year of revenue to acquire them so rest assured that big of a bet isn't so we can just convert it into a lead gen tool. We believe Trello can be much bigger that than. (Alas, I can't comment on that right now as it is in deal closure period)
If you don't use JIRA LMK what you use and what you like better. I'm always up for listening to what we are doing well and can do better.
Caveat- if you can't tell I work on BB and JIRA. If you are in SF, I'll buy you a beer & a cookie for the answers, if not I'll just keep following this thread.
BitBucket is a vital part of Atlassian's internal development process, all product teams use it on a daily basis and we treat it as a mission critical service, I'm really surprised by this comment as here in Sydney we rarely see any issues, I would be lying if some hiccups hadn't happened in the past but they were usually in very short duration, and usually only affect the UI so you can still pull/push using HTTP/SSH, moreover we have a 24/7 dedicated team to respond to any outages and there is absolutely no differences in terms of infra-structure of free vs. paid accounts inside Bitbucket, so rest assured that we put a lot of effort on making the site better for everyone.
We improved the architecture a few months ago and that should also contribute to the stability of the system as a whole, see more at: http://blog.bitbucket.org/2012/08/24/segregating-services/
And you can follow the status of the service at: http://status.bitbucket.org
We would love to hear more feedbacks like this through our usual support channels when it happens so we can investigate and improve our service.
(Disclosure: I work on Atlassian's OnDemand team).
At Atlassian (where Bitbucket now lives), we do something called FedEx (who can ship a product the fastest.) It's a 2-day sprint, where you write up a Shipment Order detailing your crazy idea, giving other people a chance to help you out if they find it interesting. At the end of it, you present what you've done, and everyone votes for a winner.
We just held one a few weeks ago, and several awesome things came out of it. One even shipped the following week: http://blog.bitbucket.org/2011/07/07/redesigned-commits-screen/
It's always a lot of fun, and this, in addition to the 20% time we get, means we get to work on really cool things which sometimes even make it to the public.
Hi! I'm a Developer Advocate over at Atlassian, and I'd like to point out that Stash offers extensible merge controls through merge request check plugins. In addition to pre-configured and third-party plugins, an open API allows you to make custom merge requirements.
https://developer.atlassian.com/stash/docs/latest/tutorials-and-examples/controlling-when-pull-requests-can-be-merged.html
In Bitbucket, we don't support this yet, but we do allow branch restrictions to ensure only trusted users are able to merge sensitive branches and many teams find this to be a suitable proxy for that behavior.
https://blog.bitbucket.org/2013/09/16/take-control-with-branch-restrictions/
That was very similar to my original aim too! I wanted it for feedback when drafting blog posts, and also to let people truly engage and critique my writing, when I'm talking about history or religion.
Your naive plan was mine too, but... then I realised that for feedback while drafting, I'd be breaking up paragraphs (with comments on them), adding new ones before commented paragraphs etc. So it never happened.
http://blog.bitbucket.org/2012/10/30/building-inline-comments-for-pull-requests-and-commits/ seems a far more technical (and reliable) way to handle these situations.
Yes, the pricing model is different with the goal of making Bitbucket affordable for individual developers and small teams, no matter whether they work on public or private projects.
Do we want people to use JIRA? If they require more than simple issue tracking, absolutely. But that doesn't mean that we aren't improving the base tools.
For example, Bitbucket already provides the ability to vote for issues and recently added rendering of the CONTRIBUTING.md file for pull requests (http://blog.bitbucket.org/2016/01/26/pull-request-guidelines-for-bitbucket-cloud).