GitLab Automatic deploy

automationgitgitlab

I will be creating a gitlab server at my school to host class code. I wish to make it so that every time any user pushes to gitlab it automatically deploys the project to /var/www/gitdeploy/<repo-user>/<repo>/<branch>, in such a way that http://<myServer>/gitdeploy/<repo-user>/<repo>/<branch> is accessible.

Preferably it would deploy all branches, but at minimum the master would be fine. All this will be running on the same server.

I heard of Gitlab CI, but wasn't to sure it was for me, and I did not understand how to set it up.

How could I do this?

EDIT:
Also, I guess I should specify that I want it for ALL users, hopefully without me configuring it for each user, ice globaly

Best Answer

You could do it with a git server-side hook (such as post-receive) that deploys your code. Gitlab CI is designed for this, however, and you should consider using it.

If you go with a hook, the hook will be a shell script in .git/hooks/post-receive/. It will need deployment credentials and you will need to write it yourself. However, that is one use case of hooks. Check out the documentation: https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks

Also see the gitlab-specific documentation: http://doc.gitlab.com/ce/hooks/custom_hooks.html

Related Solutions

GitLab post-receive hook not firing

OK, figured this one out. It's remotely possible this situation will apply to other people, so I've documented it.

Our infrastructure has all external SSH connections landing on a particular machine¹. This isn't the machine running gitlab. This wasn't obvious because gitolite+gitlab works despite this. Our homedirs are NFS mounts and both the SSH machine and the gitlab machine see the gitolite files as 'local'. The one problem with this 'distributed' gitolite+gitlab is that the post-receive hook tries to call redis-cli, a binary which doesn't exist on the machine running the hook.

To solve the problem, I installed the redis-server package on the machine accepting SSH connections (unfortunately the redis-cli binary doesn't appear to be available separately). I then modified the redis line in /home/git/.gitolite/hooks/common/post-receive to the following:

redis-cli -h hostname rpush "resque:queue:post_receive" "{\"class\":\"PostReceive\",\"args\":[\"$reponame\",\"$oldrev\",\"$newrev\",\"$ref\",\"$GL_USER\"]}" > /dev/null 2>&1

The -h hostname switch is the only addition. This causes the redis rpush command to be sent to redis on the correct machine.

The missing binary error didn't surface due to the > /dev/null 2>&1 redirect in the hook script. Although I did remove it during debugging, I must have restored it before I attempted to trigger the hook via a git push, which otherwise would have echoed the error.

My assumption about my slightly nonstandard gitlab installation turned out to be incorrect. This problem would have occured regardless; it's due to a networking quirk. Anyhow, I hope this will be of use to somebody.

In the case of git, we use external URLs even within the local network so that project URLs are consistent regardless of network environment.

Ldap – Automatic LDAP login to Gitlab

I have been having the very same problem. I wanted to authenticate through kerberos/AD and the authenticated user uses the LDAP attributes. Apache gets its credentials and sets the HTTP_REMOTE_USER and forward it to unicorn which does not know what to do with it. The solution is to force the forwarding of this variable in header, to let unicorn retrieves it, and then gitlab does the job.

RewriteEngine On
RewriteCond %{LA-U:REMOTE_USER} (.*)
RewriteRule . - [E=RU:%1,NS]
RequestHeader set REMOTE_USER "%{RU}e" env=RU

You may want to look at my problem which would provide more information. Currently, this is not (unfortunately) solved in my case implying Kerberos :/ But for your case it should work.

Best Answer

Related Solutions

GitLab post-receive hook not firing

Ldap – Automatic LDAP login to Gitlab

Related Topic