We're a pretty small team. In fact, most of the time, it's mainly me who does sysadmin/coding. This leaves very little time to develop new things, and sometimes, it doesn't even allow me to keep everything running smoothly (slowdowns/short outages always happen when I sleep.)
I realize this won't work in the long run, and something needs to be done. Therefore, I have decided to hire a bunch of people, mainly developers, but also a dedicated sysadmin and 1 or 2 UI guys (to make things prettier/more functional.) I'm currently wading through applications, and there are a lot of promising applicants in there.
Wrt/ stability, I've also provisioned 2 (much) larger instances from Amazon, where we do our hosting. We're throwing more money at this. I'm migrating a bunch of users/repositories to these larger instances today, and immediately following this, we will focus on making things faster as well.
Question was asked 2010, but I think this question needs a slightly more updated answer. I've been using Bitbucket for a few months now and as far as I can tell, it is an amazing git hosting system. You are provided with an issue tracker, wiki, unlimited public/private repositories, team collaboration, etc. Also, I have not yet encountered any downtime or slowness. On top of all of this, Bitbucket has an amazing UI, making navigating through source code and branches amazingly easy.
I would definitely recommend using this, and SourceTree.
I have not tested Bitbucket with really massive commits.
我们已经使用 BitBucket HG 大约六个月了，我毫不怀疑我们将转向不同的 VCS。它糟糕地合并了东西，在复杂的提交上犯了错误，损害了我们的生产力。我不知道HG vs BitBucket 哪些部分，但我什至没有时间去了解。当然，这是在最糟糕的情况下发生的，我们在两周内就可以交付成果。
We have been using BitBucket HG for about six months, and I have little doubt but that we will move to a different VCS. It merges things badly, makes mistakes on complex commits, hurts our productivity. I don't know which parts are HG vs BitBucket, but I don't even have time to find out. Of course this is happening at the worst time, we have a do or die deliverable in two weeks.
I've been using BitBucket for a few years 1 year at my past employer and 2 years at my present employer.
It generally works fine without any problems. However, about once a month there will be some slowness. Over this particular week there were outages spanning multiple workdays where things were slow or we were unable to push our code changes for about an hour here or there.
So to summarize, most of the time it is reliable, but occasionally, about one day a month on average it is not reliable.
发布评论
评论（4）
来自 Bitbucket 的 Jesper 在这里。
我们是一个很小的团队。事实上，大多数时候，主要是我负责系统管理/编码。这使得我几乎没有时间开发新事物，有时，它甚至不允许我让一切顺利运行（当我睡觉时总是会发生速度变慢/短暂的中断。）
我意识到这从长远来看是行不通的，并且需要做点什么。因此，我决定雇用一群人，主要是开发人员，还有一名专门的系统管理员和 1 或 2 个 UI 人员（以使事情变得更漂亮/更实用。）我目前正在涉足应用程序，并且有很多那里有前途的申请者。
关于稳定性，我还从亚马逊配置了 2 个（大得多）的实例，我们在那里进行托管。我们正在为此投入更多资金。我今天将大量用户/存储库迁移到这些更大的实例，紧接着，我们也将专注于让事情变得更快。
Jesper from Bitbucket here.
We're a pretty small team. In fact, most of the time, it's mainly me who does sysadmin/coding. This leaves very little time to develop new things, and sometimes, it doesn't even allow me to keep everything running smoothly (slowdowns/short outages always happen when I sleep.)
I realize this won't work in the long run, and something needs to be done. Therefore, I have decided to hire a bunch of people, mainly developers, but also a dedicated sysadmin and 1 or 2 UI guys (to make things prettier/more functional.) I'm currently wading through applications, and there are a lot of promising applicants in there.
Wrt/ stability, I've also provisioned 2 (much) larger instances from Amazon, where we do our hosting. We're throwing more money at this. I'm migrating a bunch of users/repositories to these larger instances today, and immediately following this, we will focus on making things faster as well.
问题是在 2010 年提出的，但我认为这个问题需要一个稍微更新的答案。我已经使用 Bitbucket 几个月了，据我所知，它是一个令人惊叹的 git 托管系统。我们为您提供了问题跟踪器、wiki、无限制的公共/私人存储库、团队协作等。此外，我还没有遇到任何停机或缓慢的情况。最重要的是，Bitbucket 拥有令人惊叹的 UI，使得浏览源代码和分支变得异常简单。
我肯定会推荐使用这个，以及SourceTree。
我还没有测试过Bitbucket 拥有大量提交。
Question was asked 2010, but I think this question needs a slightly more updated answer. I've been using Bitbucket for a few months now and as far as I can tell, it is an amazing git hosting system. You are provided with an issue tracker, wiki, unlimited public/private repositories, team collaboration, etc. Also, I have not yet encountered any downtime or slowness. On top of all of this, Bitbucket has an amazing UI, making navigating through source code and branches amazingly easy.
I would definitely recommend using this, and SourceTree.
I have not tested Bitbucket with really massive commits.
我们已经使用 BitBucket HG 大约六个月了，我毫不怀疑我们将转向不同的 VCS。它糟糕地合并了东西，在复杂的提交上犯了错误，损害了我们的生产力。我不知道HG vs BitBucket 哪些部分，但我什至没有时间去了解。当然，这是在最糟糕的情况下发生的，我们在两周内就可以交付成果。
We have been using BitBucket HG for about six months, and I have little doubt but that we will move to a different VCS. It merges things badly, makes mistakes on complex commits, hurts our productivity. I don't know which parts are HG vs BitBucket, but I don't even have time to find out. Of course this is happening at the worst time, we have a do or die deliverable in two weeks.
我已经使用 BitBucket 几年了，在我以前的雇主那里使用了 1 年，在现在的雇主那里使用了 2 年。
一般来说，它工作正常，没有任何问题。然而，大约每月一次，会有一些缓慢。在这个特定的一周里，出现了跨越多个工作日的中断，速度很慢，或者我们无法在大约一个小时内推送代码更改。
总而言之，大多数时候它是可靠的，但偶尔，平均一个月大约有一天它是不可靠的。
I've been using BitBucket for a few years 1 year at my past employer and 2 years at my present employer.
It generally works fine without any problems. However, about once a month there will be some slowness. Over this particular week there were outages spanning multiple workdays where things were slow or we were unable to push our code changes for about an hour here or there.
So to summarize, most of the time it is reliable, but occasionally, about one day a month on average it is not reliable.