2020-04-16 The switch to gitlab
Since 16/04/2020, Dropsolid Experience Cloud no longer uses git repositories on the development servers, but uses a dedicated self-managed Gitlab setup.
What's the benefit?¶
by switching to Gitlab, we give developers the possibility to use features like merge requests, visual code review, inline code changes, ...
In the future other functionality may be enabled too, like CI pipelines, fine grained project access,...
What changed in the background¶
- All repositories were moved to the Gitlab instance
- All projects were updated with the new git and gitlab url
- All users and ssh keys were synced (and are kept in sync) to the gitlab instance.
- All deploy pipelines were adapted to clone/pull from the gitlab repo's
- Project creation was adapted to create the git repository on the gitlab instance
What do I need to change?¶
The git remote of your repo¶
The git remote changed from
You most likely only need to change the remote on your local machine(s). But if you used the repo in e.g. a CI tool, please don't forget to also update the remote there
find the name of the remote pointing to the development server of your project This will most likely be
origin, and you can find it as first word on the output lines.
git remote -v origin email@example.com:/var/www/repositories/dummyproject.git (fetch) origin firstname.lastname@example.org:/var/www/repositories/dummyproject.git (push)
Update the remote with the new url structure This assumes
originis the name of the remote
git remote set-url origin email@example.com:project/dummyproject.git
Check if the remote url was updated
git remote -v origin firstname.lastname@example.org:project/dummyproject.git (fetch) origin email@example.com:project/dummyproject.git (push)
Verify you can access the new repo location This command should not give any error messages as repsonse
I get an error while cloning/pulling/pushing a repo¶
# remote: The repository url you are looking for is: firstname.lastname@example.org:project/<project_name>.git
fatal: '/var/repositories/customprojects_D8/<project_name>' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Please see the explanation above how to update the remote of your project.