From Cncz
Revision as of 10:37, 28 June 2018 by Bram (talk | contribs) (all subversion projects have been migrated quite some time ago)
Jump to navigation Jump to search

About GitLab

GitLab logo

Quote from the GitLab website

GitLab is an incredibly powerful open source code collaboration platform, git repository manager, issue tracker and code reviewer.

Our gitlab service is facing the public internet. Meaning you don't need to make use of a VPN tunnel to use it.


  • 2016-09-13 Configured reply by email. You can now simply reply by email to gitlab mail notifications.
  • 2016-07-18 Setup GitLab LFS (Large File Storage).

Maintenance window

Updates to GitLab are usually done on Friday mornings. The upgrade procedure consists of:

  • blocking ssh and http access
  • perform a backup
  • upgrade GitLab
  • test
  • restore ssh and http access

and can take up to 1 hour.

Logging in

Navigate to:

You'll see two login options:

  • Science login - for students and employees of the Science Faculty. Use your Science login.
  • Standard - for external users.

Science login

Although anyone with a Science Login can login to GitLab, only people that have actually logged in to GitLab will be visible for other GitLab users. Keep that in mind when adding people to projects or groups.

Git and managing large files

As of July 18th 2016, LFS (Large File Storage) support is enabled on the GitLab server. Git LFS allows you to manage version control on large files without storing them in the git repository. Please refer to the Git LFS project website for more information. Be aware that git-lfs works with the https transport layer (not ssh). However, since version 8.12, it's a lot easier to use:

Note: With 8.12 GitLab added LFS support to SSH. The Git LFS communication still goes over HTTP, but now the SSH client passes the correct credentials to the Git LFS client, so no action is required by the user. (source GitLab Documentation: Git LFS)

External users

Since projects are usually not restricted to employees or students of the Science Faculty, our GitLab service allows external users as well. If you wish to add external users to your GitLab project, please send a request to , mentioning the following details:

  • Desired login name - We'll prefix it with an underscore by means of avoiding collisions with our existing and future Science logins.
  • Full name - This is how you'll find the user in the GitLab system. For example, when adding the account to your project.
  • Mail address. GitLab will use this mail address to send an automatically generated mail with instructions to set a password.

As soon as Postmaster created the account, you should be able to add the external login as a member your project. We're not yet sure whether external users should have the option to create projects, so the project limit for external users is set to 0 initially. Depending on the kind of work flow (gitlab merge requests, etc), it might be necessary to give external users the option to create one or more projects.

Ideally, postmaster should not be 'in the loop' and users with a Science login should be able to create external user accounts themselves, however there seems to be a bug in the GitLab API that prevents us from setting this up.


Keyboard shortcuts

Press ? to display all available keyboard shortcuts!

Manual migration from Subversion

Inspired by this short manual, an SVN to git conversion could boil down to something like:

cd /tmp/
git svn clone --no-metadata -A users.txt
cd myproject
git remote add gitlab :yourscienceloginname/myproject.git
git push --set-upstream gitlab master

Git URLs (https and ssh) are shown on the top of the project page in gitlab. The generic repository URL for the science SVN server is:{repository}

And for CS:{repository}

You can also see this for public svn repositories on (viewing private repositories requires authentication).

Instructions displayed when creating a new project

Just copied them over here, because these instructions are only displayed when your project does not yet contain any files.

Git global setup

$ git config --global "Your Name"
$ git config --global ""

Create a new repository

$ mkdir newproject
$ cd newproject
$ git init
$ touch
$ git add
$ git commit -m "first commit"
$ git remote add origin :yourscienceloginname/newproject.git
$ git push -u origin master

Push an existing Git repository

$ cd existing_git_repo
$ git remote add origin :yourscienceloginname/newproject.git
$ git push -u origin master