undefined | Better HN

0 pointsest7y ago0 comments

everything works great on gitlab, until the moment you had to migrate.

Landmine experience in issue lists

0 comments

4 comments · 1 top-level

dsumenkovic7y ago· 3 in thread

Hi, Community Advocate from GitLab here. Could you please reference what issues you are experiencing? We'd love to follow up on it.

Also, if you want to write the details, it would be great to open an issue https://gitlab.com/gitlab-org/gitlab-ce/issues. Thanks in advance.

estOP7y ago

Hi,

https://gitlab.com/gitlab-org/gitlab-ce/issues/27217

Something like this. When I fixed the VERSION manually, there are other errors, as expected.

However the peculiar thing is the errors are not idempotent. Somethings there's some postgres wrong column error, other times it says you can't import the project because you can't have hyphens in project names. (which I don't)

Migration is hard, considering everything can be linked in Gitlab.

Aeolun7y ago

One, having to come from the same version.

Two, having to connect to the same block storage in exactly the same way to make everything work.

I just want to upload a backup that gitlab makes, and upload that somewhere (anywhere) to restore from that one tarball, regardless of where I’ve decided to host my current instance or data (or indeed, if I’ve decided to use block storage again or not).

sytse7y ago

Thanks for the feedback.

1. Yes, you have to restore a backup on exactly the same version of GitLab and then upgrade that version. If you restore it to a different version the database scheme isn't correct.

2. You can restore a GitLab backup anywhere https://docs.gitlab.com/ee/raketasks/backup_restore.html as long as it is the same version. I think the output is a single file.

1 more reply

j / k navigate · click thread line to collapse