Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

BitBucket was down

status.bitbucket.org

Post reply on HN
Print view View original

51–55 of 55 posts

Re: BitBucket was down

#51

Post by akerl_ »

kevinburke wrote: post #29
keehun wrote: post #22

Earlier quoted context omitted.

I doubted that Github would push new (bad) production code mid-day unannounced, and it still happened. To be fair, Github I think pushes new production code several times a day every day?

If you are pushing new configuration at 6am on a Sunday, and things immediately stop working, you revert the configuration change.

If you work in an environment where such rollbacks are that simple, you're in the rare minority. The reality of working with large-scale distributed systems is that rolling back becomes much more complicated. Push out new code and the accompanying DB schema change? Good luck rolling back to the older schema when you find the bug.

Re: BitBucket was down

#52

Post by rst »

Achshar wrote: post #38
lighthazard wrote: post #33

So how much does this affect work flow for Git? Doesn't seem like that much of a big deal for small downtime unless I'm hosting a public page or open source project. I, personally, use Bitbucket for the unlimited private repos, makes development easy for me so downtime doesn't affect my team that much since we can pull from each other still.

How do you pull from your team members when hosting site is down?

If you have ssh access to their machines, you can just set up their repo as a new remote.

If not, "git bundle" supports coordination via email, which is the workflow that git was originally designed to support.

Re: BitBucket was down

#53

Post by jamesRaybould »

seacious wrote: post #44
jamesRaybould wrote: post #31

Earlier quoted context omitted.

Surely its not about outsourcing a status page but just making sure that it is on completely different infrastructure?

Outsourcing allows you to isolate the status page from your human infrastructure. If your team makes a bad decision that leads to an outage then they can make the same bad decision about your status page if they are in charge of that as well. This provides a form of human fault tolerance.

I agree that insulating against human fault is always a good thing to do but at some point you must trust your team to do the right thing. In fact in using a 3rd party you are trusting that said 3rd party also has a form of human fault tolerance.

That said I cannot imagine even the most incompetent team making a change to the status page, which I would always host on completely separate infrastructure, at the same time as the rest of production infrastructure.

Re: BitBucket was down

#54

Post by spiffyman »

korzun wrote: post #14
rgvcorley wrote: post #3

The uptime for GitHub for 2013 was 99.69%, according to http://www.getapp.com/compare/source-code-management-softwar... . I can't find a stat for BitBucket, does anyone know? I'm considering switiching to GitHub for a private repo I'm currently hosting on BB, due to downtime.

I would also like to point out (as a heavy user of both platforms) that BitBucket has outages that do not 'register' as an outage. There are issues like hanging on pull requests/merges at random or not loading the diff. Frustrating.

GitHub has this issue, too. Try doing a PR on GH when the diff is reasonably large. We get 500s from them when trying to review anything worth doing. That and the inability to set permissions on branches have prevented us from moving from self-hosted Gitolite to GH full time.

Re: BitBucket was down

#55

Post by korzun »

spiffyman wrote: post #54
korzun wrote: post #14

Earlier quoted context omitted.

I would also like to point out (as a heavy user of both platforms) that BitBucket has outages that do not 'register' as an outage. There are issues like hanging on pull requests/merges at random or not loading the diff. Frustrating.

GitHub has this issue, too. Try doing a PR on GH when the diff is reasonably large. We get 500s from them when trying to review anything worth doing. That and the inability to set permissions on branches have prevented us from moving from self-hosted Gitolite to GH full time.

You should try BitBucket, just too see how hard it bails on you.
Post reply on HN