... | ... | @@ -18,6 +18,16 @@ Migration support is available through the [inria helpdesk](https://helpdesk.inr |
|
|
|
|
|
A mattermost channel is also available https://mattermost.inria.fr/devel/channels/gforge-gitlab (but remember that the preferred way to ask for support is through the helpdesk because support tickets can be correctly tracked)
|
|
|
|
|
|
## gitlab project setup
|
|
|
|
|
|
A gitlab project needs to be created. It's up to you to choose between private / internal / public project (see https://gitlab.inria.fr/help/public_access/public_access.md). You can choose between a project in a user namespace or in a group namespace (see https://gitlab.inria.fr/help/user/group/index.md#namespaces)
|
|
|
|
|
|
Projects members need to have an account on the gitlab. If they don't have an account, they need to create one. It will then be possible for them to request access to the project (but only for public projects) or the opposite, an administrator can manually add them.
|
|
|
|
|
|
Project name and user names do need necessarily need to be the same between gforge and gitlab (though it may be simpler, if they are the same).
|
|
|
|
|
|
Also don't forget that to be able to actually do something (like cloning, pushing...) users need to setup their account correctly. If they want to use ssh to avoid entering their username/password on each action, they should have a working ssh and upload their key to the gitlab (the same as with the gforge)
|
|
|
|
|
|
## Migration of source control repositories
|
|
|
|
|
|
INRIA gitlab is restricted to git (no subversion anymore), so for subversion users unfamiliar with git, you should take the time to read and understand the basic differences between subversion and git. If you want to stay with subversion, there is no alternative at INRIA, but you can go to SourceSup https://sourcesup.renater.fr/, which is actively maintained by Renater.
|
... | ... | |