Re:Scaling Bitbucket’s Database
by doubleunplussed on Saturday February 15, 2020 @02:18PM
(#22337278)
Still salty about them dropping mercurial support without providing any migration tools, and planning to just delete data without any archiving.
[ Parent
| on HN ]
Also salty!
For hg->git migration, https://github.com/frej/fast-export worked smoothly for me.
mkdir new-git-repo
cd new-git-repo
git init
fast-export/hg-fast-export.sh -r ../path-to-old-hg-repo
(probably want to translate .hgignore to .gitignore and commit it)
git remote add origin git@path_to:git_server
git push -u origin master
git push --all
Re:Scaling Bitbucket’s Database
by johannes1234321 on Saturday February 15, 2020 @07:54PM
(#22339128)
Yes, it is fairly easy to convert the repo, but
1) this afaik couldn't be done inside the BB project, so one would have had to create a new repo and lose bug history etc.
2) It's a trust thing. If BB kills repos once, who doesn't say they won't kill others tomorrow?
3) Comfort: Import to GitHub is a click away
Re:Scaling Bitbucket’s Database
by michaelhoffman on Saturday February 15, 2020 @05:46PM
(#22338561)
Same here. I don't love that they aren't going to support Mercurial anymore. But deleting all our existing projects without providing a path for us to migrate or archive? I can't trust them anymore.
I'm also salty. What's your plan? I'm either gonna migrate to git (and use a different host), or self-host something like hetapod.net
I went to sourcehut. I am very happy, but during the process I ended up actually having to learn a bit of git. Future projects will probably be git.
Re:Scaling Bitbucket’s Database
by doubleunplussed on Sunday February 16, 2020 @02:07AM
(#22340264)
Yeah I'm moving to git and github. I always pteferred mercurial for what I maintain are good reasons not just of personal taste, but I've been swimming against the tide for too long and it makes sense to go with git and github.
If github goes downhill, at least I'll be in good company next time!