We’re migrating repositories to new hardware

By on April 22, 2014

Starting today, we will be migrating all repositories to a new storage system which will allow us to improve the service and reliability of Bitbucket.

Over the next weeks, you can expect the following:

Due to the nature of the migration, we are unable to provide specific timelines for when individual repos will be affected. However, we expect no more than a 10 minute disruption when your repository will be placed in read-only mode.

Thank you all for your patience and support! We are working hard to constantly build a better Bitbucket.

If you have any other questions or concerns, please come to support@bitbucket.org.

129 Comments

  • iSynth
    Posted April 22, 2014 at 2:54 pm | Permalink

    Thanks for your work guys! I really like your repository hosting service!

  • Martín
    Posted April 22, 2014 at 3:21 pm | Permalink

    Great! :3

  • Anonymous
    Posted April 22, 2014 at 3:55 pm | Permalink

    Thank you for working hard 🙂

  • Paul O'Flynn
    Posted April 22, 2014 at 4:00 pm | Permalink

    Um, any hint as to when and for how long? This is kind of important!

    • Posted April 22, 2014 at 4:36 pm | Permalink

      Good question.

    • Mahmoud Hussien
      Posted April 22, 2014 at 11:15 pm | Permalink

      yes plz give us an estimated time

      • Liam Smythe
        Posted April 24, 2014 at 2:23 am | Permalink

        It’s impossible to give an estimated time due to the vast quantity of repositories, and if you read the post, you’ll notice this ”
        On average, each repository should take less than 10 minutes to migrate, but repositories with frequent updates may take longer (up to 30 min in rare cases).”

        • Paul A
          Posted April 24, 2014 at 1:01 pm | Permalink

          2 days ago this post had non of that info.

          • Liam Smythe
            Posted April 25, 2014 at 1:58 am | Permalink

            Ah, sorry about that, I didn’t realise.

          • SwagLord
            Posted April 30, 2014 at 8:28 am | Permalink

            noooooooooooooooob

  • Guest
    Posted April 22, 2014 at 4:37 pm | Permalink

    Gracias amigos!

  • Anonymous
    Posted April 22, 2014 at 4:37 pm | Permalink

    Thanks for the update!! Keep up the great work!

  • Michael
    Posted April 22, 2014 at 5:56 pm | Permalink

    Thank you guys

  • Posted April 22, 2014 at 6:06 pm | Permalink

    yeah!
    Thanks guys..

  • Anonymous
    Posted April 22, 2014 at 6:29 pm | Permalink

    Thank you Guys!

  • Humbal Shahi
    Posted April 22, 2014 at 7:53 pm | Permalink

    Thank you guys!

  • Posted April 22, 2014 at 8:25 pm | Permalink

    Thanks for your great work.

  • Anonymous
    Posted April 22, 2014 at 9:42 pm | Permalink

    It would be great if you guys give us a schedule of when this is happening…

  • Ramakrishnan
    Posted April 22, 2014 at 10:06 pm | Permalink

    What is the time window for downtime?

  • Anonymous
    Posted April 22, 2014 at 10:12 pm | Permalink

    So is there any issues about post hook? My hook didn’t work after 12:06+08:00 which is my last push. If not, I will check other issues. Thank you!

  • Anonymous
    Posted April 22, 2014 at 10:13 pm | Permalink

    Is the migration done ?

  • reza
    Posted April 22, 2014 at 10:58 pm | Permalink

    Thank you very much for your great work!

  • Eric Xavier
    Posted April 22, 2014 at 11:10 pm | Permalink

    Thank you Bitbucket!!

  • SapiterbangID
    Posted April 22, 2014 at 11:21 pm | Permalink

    thank you, good luck matey 🙂

  • chromeinfotech
    Posted April 22, 2014 at 11:25 pm | Permalink

    Thanks you for great work. I have a one question, How long it will take?

  • Chetan Vaity
    Posted April 22, 2014 at 11:49 pm | Permalink

    Which repositories? All or some of them? Should all repo owners be concerned about this? Please give timelines.

  • Caz
    Posted April 23, 2014 at 12:04 am | Permalink

    Please can we have a timescale? I feel rather annoyed that no notice was given of this.

  • Rhys
    Posted April 23, 2014 at 12:32 am | Permalink

    Any news on timescales?

  • Posted April 23, 2014 at 12:48 am | Permalink

    Our students projects are in their final sprint. Please tell us how to determine which repositories will be affected, so that we can use a backup solution ahead of time.

    Thanks in advance.

    • Mr. Popo
      Posted April 23, 2014 at 6:44 am | Permalink

      If you are using git… this isn’t an issue at all. Just launch any ol’ writable server, and git will somehow handle writing to it. Doing so via SSH would be nice. Viva Distributed SCM!

    • Anonymous
      Posted April 24, 2014 at 5:47 am | Permalink

      Even if you need to share you can add another remote and work with that as an emergency plan 🙂

  • Emmett
    Posted April 23, 2014 at 1:56 am | Permalink

    We have created a new project but cannot Pull / Push to it.

    Is this related to the repositories move?

    Thanks.

    • Łukasz Żak
      Posted April 23, 2014 at 2:50 am | Permalink

      I think yes:
      “During this transition your repository will temporarily be placed into read-only mode to ensure data integrity”

      • Laurens
        Posted April 24, 2014 at 10:56 am | Permalink

        No, because read-only means that you CAN pull.

  • Posted April 23, 2014 at 2:01 am | Permalink

    is there any email notification when we get access to write in our repo? this is important because we do not get worried about the pushing for a long/unknown time

  • L
    Posted April 23, 2014 at 2:31 am | Permalink

    A timeframe would indeed be important as all teams of the https://helloworldopen.com competition have private BitBucket repos for their code. Well, that, and professionals, I guess.

  • Dilip
    Posted April 23, 2014 at 3:05 am | Permalink

    You guys are doing great. But please mention timeline of your maintenance. Thanks 🙂

  • Ruchir
    Posted April 23, 2014 at 4:05 am | Permalink

    Can You Please provide the planning dates or something which help us to plan according to ?

  • Albert-Jan
    Posted April 23, 2014 at 4:41 am | Permalink

    Thanks for all the hard work Bitbucketeers! Git is designed with this kind of situations in mind so it’s no problem at all for me.

  • michael
    Posted April 23, 2014 at 6:20 am | Permalink

    seems like I am not receiving any emails from bitbucket currently? Anyone the same problem?

  • Posted April 23, 2014 at 6:37 am | Permalink

    Let’s Go Atlassian

  • Germán Larraín
    Posted April 23, 2014 at 6:47 am | Permalink

    Not providing a timeframe nor fail to warn users ahead of time doesn’t speak well of Bitbucket

  • maticeder
    Posted April 23, 2014 at 7:44 am | Permalink

    Thanks Guys!

  • EricG
    Posted April 23, 2014 at 7:52 am | Permalink

    Thank you Bitbucket, great service so far and exactly what I need for my side-projects.

  • Napster85
    Posted April 23, 2014 at 8:11 am | Permalink

    Keep calm and carry on. Good luck 😉

  • aaa
    Posted April 23, 2014 at 8:12 am | Permalink

    aaa

  • aaa
    Posted April 23, 2014 at 8:13 am | Permalink

    sfsdewrew

  • Cameron Banga
    Posted April 23, 2014 at 8:58 am | Permalink

    Estimated time window and anticipated period this could last? Kinda a bigger situation and seems like this announcement is missing some major details.

  • Eddy Ferreira
    Posted April 23, 2014 at 9:11 am | Permalink

    my team members are having permission problems accessing newly created repository’s that they should have access to. any update when the migration will be finished?

  • Anonymous
    Posted April 23, 2014 at 10:24 am | Permalink

    We’ve listened to your feedback and made changes to both our process and this blogpost to reflect those changes. Please email support@bitbucket.org with any other specific concerns.

    • tcbarrett
      Posted April 26, 2014 at 12:55 am | Permalink

      Thank you for investing in your product/service in order to make things better for us. Much appreciated.

    • Posted April 26, 2014 at 8:40 pm | Permalink

      Maybe you guys should make that a featured comment. Hover over your comment, click the top right arrow, and feature it. That way, it will stay pinned to the top of the thread and everyone will see it.

  • JohnnyCash
    Posted April 23, 2014 at 11:32 am | Permalink

    FFS guys, stop crying!
    They said that the migration would take within 10 to 30 minutes. Nothing to go crazy over. You most likely won’t even notice your repository went down.

    • Anonymous
      Posted April 27, 2014 at 7:47 am | Permalink

      Well I guess people are noticing now 😛

      • Omar Al-Ithawi
        Posted April 28, 2014 at 2:36 am | Permalink

        Yes, we do!Example:

        npm install sax@”>=0.1.0 <0.2.0"

        npm install :

        Install a package by cloning a git remote url. The format of the git url is:

        ://[@][#]

        is one of git, git+ssh, git+http, or git+https. If no is specified, then master is used.

        Examples:

  • Hermes Alves
    Posted April 23, 2014 at 12:26 pm | Permalink

    Obrigado! from Brazil 😉

  • Nicolás Vélez Franco
    Posted April 23, 2014 at 3:40 pm | Permalink

    Thank you

  • Dave Richer
    Posted April 23, 2014 at 9:24 pm | Permalink

    I very much hope everyone who is complaining is at least a paying customer. I am utilizing your free services and there for I thank you for providing them to me and you can take how ever long you want to doing the things you do without nothing but gratitude from me lol

    • Glen H
      Posted April 24, 2014 at 5:24 pm | Permalink

      I agree. Half an hour of repository downtime, especially for a free service, is nothing to complain about. You can still develop on your local machine for that extremely long period of a few minutes, and contributors can still pull the source from the server.

      • Posted April 24, 2014 at 5:26 pm | Permalink

        Plus, one of the many strengths of git make downtime almost irrelevant. 🙂

  • Nepali
    Posted April 23, 2014 at 11:23 pm | Permalink

    Thank you for your great work.

  • yoshi
    Posted April 24, 2014 at 12:35 am | Permalink

    Thank you

  • Posted April 24, 2014 at 12:50 am | Permalink

    Terima Kasih – a thank you from Indonesia 🙂

  • Jan
    Posted April 24, 2014 at 2:02 am | Permalink

    Great, keep up those improvements. Thanks for putting this notice on bitbucket.org too.

  • BOURNE EXCELENSIA
    Posted April 24, 2014 at 2:18 am | Permalink

    There is nothing to Worry about I believe, Even though I push and pull a lot, There is a little chance I will be caught up during that 10 minutes, or say 30 minutes.

  • sweet potato
    Posted April 24, 2014 at 2:21 am | Permalink

    Imma sweet potato

  • Sandeep Gupta
    Posted April 24, 2014 at 2:57 am | Permalink

    Keep up the good work!

  • Yusuf Özer
    Posted April 24, 2014 at 3:41 am | Permalink

    I am newbie about git.. Using git and your website since 1 weak… But i can tell you that, i love Atlassian… Thank you for your services…

  • Matt Butterworth
    Posted April 24, 2014 at 3:44 am | Permalink

    I wonder how many people actually read before they moan about stuff. Appalling. Thank you for all your hard work!

  • Anonymous
    Posted April 24, 2014 at 3:45 am | Permalink

    I get timout when I pull from the repository to my server. On the local works, but on server is not. Any ideea?

    ssh: connect to host bitbucket.org port 7822: Connection timed out
    fatal: The remote end hung up unexpectedly

  • Posted April 24, 2014 at 5:17 am | Permalink

    I am not a paying user so I appreciate the service as it is. Thanks guys. For paying users I’d recommend having some info box with a proposed migration time/date under their account (to manage expectations).

  • Giovanni Pires da Silva
    Posted April 24, 2014 at 5:35 am | Permalink

    Hm, thank you, no problem. As long as you notify us when it will be happening, there’s no problem. Thanks again. Go on. 🙂

  • Rich Wandell
    Posted April 24, 2014 at 7:02 am | Permalink

    Will we be notified before this is done on one of our repositories?

    • bfetler
      Posted April 24, 2014 at 11:32 am | Permalink

      Good question. It would be nice if they emailed the repo owner a day beforehand. At least they let us know they were doing it ahead of time. Thanks as always to the BitBucketeers.

  • Anonymous
    Posted April 24, 2014 at 7:20 am | Permalink

    And there will be a way to tell if my repository is already migrated or not? Thanks

  • Bradden Gross
    Posted April 24, 2014 at 8:19 am | Permalink

    Pull requests with conflicts are no longer giving me the ability to update. I need to make a new, identical pull request. Is this related to the migration?

    • Joey
      Posted April 25, 2014 at 11:20 am | Permalink

      I have been having the same problem, so to get around this I would attempt to make a new Pull Request then it recognized that there was already a PR out there for that branch and it said that it would just update the other PR.

      In another case, I just declined the original PR and made a new one, but that was before I learned that it would recognize one was already created for that branch and just update.

      • Bradden Gross
        Posted April 25, 2014 at 12:01 pm | Permalink

        Hey Joey,

        I was doing the same but I’ve now found it easier to just click the edit button on the pull request and it seems to pick up the changes and then I’ll just save it. Still not as good as it was, though.

  • Chris Vartavarian
    Posted April 24, 2014 at 11:10 am | Permalink

    Thank you for the info. Fingers crossed that no glitches occur during the migration

  • rahul bawa
    Posted April 24, 2014 at 11:17 am | Permalink

    Before i begin i must thank you guys for AWESOME service that you are providing.

    Your warning on the dashboard says that “SOME REPOS” will be migrated but the blog says all repositories.If some will be moved , can you send a mail to those and if all will be migrated,Can you specify when ?

  • Posted April 24, 2014 at 11:23 am | Permalink

    date and commit messages are missing next to files in source, is this due to migration?

  • Khan
    Posted April 24, 2014 at 11:32 am | Permalink

    Please don’t cry over repository migration, it will take from 10 to 30 mins..and i agree with Johnny cash as most of all wont even notice. It might increase their productivity and ease our life. Keep doing the good stuff..carry on Bits into Buckets.

  • Daniel Jimenez
    Posted April 24, 2014 at 1:40 pm | Permalink

    Wow, I’m noticing bitbucket seems a lot faster since this notification went up. Well done!

  • Posted April 24, 2014 at 1:46 pm | Permalink

    Is that why git push is hanging for me?

    I also tried “ssh -T git@bitbucket.org” and that also hung, so I wonder if there’s something else wrong.

  • Posted April 24, 2014 at 4:23 pm | Permalink

    You guys rock! Good luck! 🙂

  • Harold Gillespie
    Posted April 24, 2014 at 8:14 pm | Permalink

    Yes thanks. As Yoder said” have have having not is no”

  • Kike
    Posted April 25, 2014 at 1:20 am | Permalink

    It will be a great idea to know the state of every repository, migrated or not migrated,
    Greetings.

  • Junaid Atique
    Posted April 25, 2014 at 3:20 am | Permalink

    We love your service and we knew that anything you do will make the service more promising. Thank you for providing us Bit bucket.

  • Posted April 25, 2014 at 6:36 am | Permalink

    Will we get an email alert when our repos are being migrated, or should be just be on the lookout for git errors?

    Thanks for the great service!

  • Guest
    Posted April 25, 2014 at 9:44 am | Permalink

    Thanks for your great work!

  • Posted April 25, 2014 at 9:46 am | Permalink

    Good luck and thanks for your work!

  • Hadi Irvani
    Posted April 25, 2014 at 10:00 am | Permalink

    fingers crossed from the PeachDish.com Team that it goes alright!

    Thanks for having a great Product!

  • Anonymous
    Posted April 25, 2014 at 10:02 am | Permalink

    in the post it clearly says it will take 10-30 minutes, unless this was just updated.

  • Dewa Rama
    Posted April 25, 2014 at 11:35 pm | Permalink

    Sounds like a good news, thank you!

  • Jairo Alonso Fernández Vega
    Posted April 26, 2014 at 4:10 am | Permalink

    Gracias por continuar mejorando!!!

  • Danut Mihai Florian
    Posted April 26, 2014 at 9:34 am | Permalink

    Thank you for your great and professional services!

  • rex2002xp
    Posted April 26, 2014 at 10:39 am | Permalink

    excellent news, you have good luck!

  • Amgad Suliman
    Posted April 26, 2014 at 9:30 pm | Permalink

    I don’t think this will be an inconvenience to anyone since both Git and Mercurial are distributed. Thank you for your hard work.

  • Gibbo
    Posted April 27, 2014 at 6:57 am | Permalink

    Thought I would drop in and have a read, I assume that this is why most of the time my most used repo is acting strange?

    It sometimes never loads, or is very slow, some buttons literally “Don’t respond”, such as the upload button on the downloads page.

    Anyone confirm? 😀

  • Posted April 27, 2014 at 9:22 pm | Permalink

    Hello, the homepage is not loading.

  • Олег Абражаев
    Posted April 28, 2014 at 1:50 am | Permalink

    I’m have this error right now.

    It’ becouse my repo moving on new server?

    https://bitbucket.org/site/master/issue/9377/remote-error-unable-to-create-temporary

  • comzine
    Posted April 28, 2014 at 3:32 am | Permalink

    Thank you for the information!
    I was just wondering why pushing to remote is not working at the moment 🙂

  • Posted April 28, 2014 at 7:54 am | Permalink

    I’m getting 500 errors for bitbucket.org in general this morning. Are these issues related to the hardware upgrades?

  • Ronny
    Posted April 28, 2014 at 8:13 am | Permalink

    It’s now very slow !!! Pull/Push timeout 🙁

  • Vijay
    Posted April 28, 2014 at 8:24 am | Permalink

    fatal: unable to access ‘https://*******************.git/’
    : Empty reply from server.

    Why i get empty reply from server?
    what should i do?
    Plz help.

    Thank you in advance.

  • Posted April 28, 2014 at 10:06 am | Permalink

    Hi Atlassian, just wanted to drop info on another bug. I have two repos that should have been imported from my Github account by now, but they have been stuck in the “importing” state since 10:40 ET. Not sure if those particular repos are affected by the upgrade (LDC and Minix) but it appears they’re in import limbo.

  • Guest
    Posted April 28, 2014 at 10:47 am | Permalink

    Looks like BitBucket is up and down. Crashing A LOT. We’re not able to get much done because of it. I think the “up to 30 min” quoted above was a bit too optimistic.

  • Guest
    Posted April 28, 2014 at 7:52 pm | Permalink

    Are the repositories still having problems? I can’t build from Bamboo

    com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://x@bitbucket.org/xx failed with code 128. Working directory was [.]., stderr: [error: The requested URL returned error: 503 while accessing https://x@bitbucket.org/xx/info/refs, fatal: HTTP request failed])

  • Diego Arrieta
    Posted April 28, 2014 at 8:02 pm | Permalink

    Great!!! i wish you the best!!!!!

  • Posted April 28, 2014 at 10:28 pm | Permalink

    Thanks for the notice!

  • Peter
    Posted April 29, 2014 at 2:01 am | Permalink

    Hey guys,
    thank you for all services! You are making the World better.
    Could you look at smart commits 🙂 Seems like something went wrong with this. JIRA do not understanding our BitBucket from yesterday 🙁

  • Posted April 29, 2014 at 2:05 am | Permalink

    How to dismiss the announcement banner? It makes me nervous

  • Hossein
    Posted April 29, 2014 at 2:49 am | Permalink

    But it looks we have problems since yesterday afternoon and still problem is there, sometimes we could push sometimes not!

  • Marcin
    Posted April 29, 2014 at 3:23 am | Permalink

    Big thanks. Good JOB.

  • JM
    Posted April 29, 2014 at 3:36 am | Permalink

    Thanks for the work. Always appreciated

  • Posted April 29, 2014 at 4:59 am | Permalink

    Merci !

  • Honza Pobořil
    Posted April 29, 2014 at 5:12 am | Permalink

    Btw, if you really need to sync changes with coleagues, you can use git’t native abilities to connect remote to every machine with ssh access.

  • drobban
    Posted April 29, 2014 at 5:20 am | Permalink

    Well, my repos is down? Is it caused by this migration or something else?

  • Jeremy Steele
    Posted April 29, 2014 at 7:23 am | Permalink

    So… whats up with all the crazy slowness lately? For example – starting a push or pull takes forever initially, but goes quick once it gets going. Was good 2 days ago.

  • bddrhg
    Posted April 29, 2014 at 8:42 pm | Permalink

    For how much money I pay… no wait… free unlimited repos? You guys do a great job. Thanks!

  • Tirta Lalondong
    Posted April 29, 2014 at 9:36 pm | Permalink

    Keep up the good work guys. Thank you so much 🙂

  • Ano Van
    Posted April 30, 2014 at 12:26 am | Permalink

    we always support you, we use the best service of bitbucket, my regards http://www.pasarkode.com

  • Posted April 30, 2014 at 8:23 am | Permalink

    Thanks for upgrading your service. 10-30 mins is very reasonable, given that most of the repositories on here are probably with free accounts. Even as a paying subscriber I don’t find that sort of outage a problem, especially with such advance notice.

    Cheers for being a great service for the software community!

  • noureddine
    Posted April 30, 2014 at 3:38 pm | Permalink

    merci

  • Md. Arman Kabir
    Posted May 1, 2014 at 8:13 am | Permalink

    i cant synchorize now! 🙁 time our and no reponse return code 255

  • Chris Beck
    Posted May 1, 2014 at 10:44 am | Permalink

    I want to echo everyone’s sentiments. This is an phenomenal free service and goes nicely with my paid for JIRA, Confluence, HipChat troika.

  • Posted May 1, 2014 at 10:58 am | Permalink

    Thanks!

  • SlyOtis
    Posted December 5, 2015 at 12:42 am | Permalink

    Love you, sucks with down time but no problemo, peace