Live data from Hacker News

BitBucket was down

status.bitbucket.org

41–50 of 55 posts

Re: BitBucket was down

#42
post #38

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?

git remote set-url origin link I set a new remote which would be a server we host that is also running git, or one of our personal computers will act as the remote until Bitbucket is back up. the thing is, the service hasn't been down for long periods of time, so the normal mode of operation is to push locally until we need to push to remote, which Bitbucket usually is up.

Re: BitBucket was down

#43
post #38

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?

For Mercurial, you'll need to run "hg serve" to have a lightweight Mercurial server up and running, so other developers can pull from you just like from any other repository:

    hg pull -r deadbeef http://developer-01:8000/
Remember, we're in DVCS land here.

Re: BitBucket was down

#44

Earlier quoted context omitted.

status.bitbucket.org is hosted on Statuspage.io. It would be rather silly to host your status page on your main production infrastructure since if it goes down so does your status page. Personally unless you're a major player I think you should always outsource your status page.

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.

Re: BitBucket was down

#45
post #8

While I don't have anything smart to say about stuff like this, I'd love to see their postmortem on this one. Would be somewhat hilarious if it's another bad configuration push across their infrastructure. Github has had so many of them and especially with the recent article of the stock brokerage firm going bankrupt due to bad configuration/code push.

I doubt they are pushing new configuration at 6am on a Sunday morning.

[deleted]

Re: BitBucket was down

#46
post #38

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?

One of the the nice things about a DVCS is that you can do something like work with as many copies as you need - there's no downside to pushing a copy out to a spare server where everyone can access via SSH until the main repo is back online.

Re: BitBucket was down

#47

Yet another reason to self-host GitLab[1] or HgLab[2]. [1]: https://www.gitlab.com/ [2]: http://hglabhq.com/

Then, when it goes down you gave to deal with it instead of someone else!

There's usually a curve where it makes sense to invest in self-host, but the Bit bucket Slate has been really great.

Re: BitBucket was down

#48
post #20
post #18

Earlier quoted context omitted.

A firm going bankrupt due to a bad code/config? Do you have a link to the article you're referring to? Sounds interesting...

$400 million down the drain http://dougseven.com/2014/04/17/knightmare-a-devops-cautiona...

Just the fact that they didn't have a way to record and verify whether the deployment was done properly boggles my mind. When I worked at a bank we had package management to do deployments, a separate tool for taking inventory of installed software (in case of users managing to sneak third party programs on to their system), and on top of that a web framework for tracking milestones during projects that allowed for manual entry by technicians and automated input from scripts so tasks that had to be done by hand like replacing hardware could be coordinated with build scripts and management could monitor the whole thing from a dashboard.

Re: BitBucket was down

#49
post #27

Why are they not hosting it on the status.bitbucket.org server? Tt have never been down as far as I know!

status.bitbucket.org is hosted on Statuspage.io. It would be rather silly to host your status page on your main production infrastructure since if it goes down so does your status page. Personally unless you're a major player I think you should always outsource your status page.

Then why don't they host their main servers on statuspage.io? I've never seen a status page that is down.

Re: BitBucket was down

#50
post #38

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?

You can at the very least send each other a zip file containing the .git directory. When you extract that directory into a separate directory, you can add it as a remote and fetch/pull from it (because that's the entire repository right there).

What I usually do is I copy the .git to another name before running zip, so it doesn't extract as .git :)

This is also one of the reasons you shouldn't commit binaries, especially large ones.

Post reply on HN