Re: [GitLab CI] How to pull from GitLab's Docker Registry in .gitlab-ci.yml?

de? > > Regards, Jens have you tried to set the "Visibility Level" of the project to "Public"? regards Markus Köberl -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Laboratory E-mail: markus.koeb...@tugraz.at

gitlabhq@googlegroups.com

,ou=user,dc=EXAMPLE,dc=COM"} g = Gitlab.client info=g.create_user('ldap.u...@example.com','xx',options) g.add_group_member(,info.id,) To find out the you can use the gitlab CLI: gitlab groups And you get the permissions of a user for a group with (access_level):

Re: Disable account confirmation for users created using the API

uld be a good idea to create a bug report and add your patch. I see no reason why it would make sense if an admin creates an user using the api that the user has to confirm the mail address. -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Laboratory E

Re: Unable to restore a backup (seems to be if the project hasn't been 'pushed' to yet)

advice :) Today I encountered the same problem with gitlab 7.4.0 omnibus debian deb during my update procedure to 7.4.2. Any ideas how to fix this? I do have a test system so it's save for me to perform some tests... I will wait with updating my production environment till I am sure it is p

gitlab-ci

ing around with the code? regards Markus Köberl -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Laboratory E-mail: markus.koeb...@tugraz.at

Re: gitlab-ci

On Wednesday 03 December 2014 11:29:43 Jeroen de Neef wrote: > Hi Markus, did you make the crontab in 'crontab -e'? It got automatically generated: # Chef Name: gitlab-ci schedule builds 0 * * * * /opt/gitlab/bin/gitlab-ci-rake schedule_builds -- Markus Koeberl Graz University

Re: gitlab-ci

get added again the next time i run gitlab-ctl reconfigure -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Laboratory E-mail: markus.koeb...@tugraz.at

backup restore rebuild authorized_keys

unattended in a script: This will rebuild an authorized_keys file. You will lose any data stored in authorized_keys file. Do you want to continue (yes/no)? yes Thanks Markus Köberl -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Laboratory E-mail: markus.koeb

Re: backup restore rebuild authorized_keys

riable force gets evaluated. So that if I set force=yes the authorized_keys file gets rebuild: force=yes gitlab-rake gitlab:backup:restore BACKUP= This solves my problem. Thanks Markus Köberl -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Labor

fatal error at clone and pull over https

ing debian wheezy. Does somebody know if git is compiled with pthread support on debian or how to activate it in the gitlab code? regards Markus Köberl -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Laboratory E-mail: markus.koeb...@tugraz.at

500 page while Authorize gitlab-ci

e the problem here? regards Markus Köberl -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Laboratory E-mail: markus.koeb...@tugraz.at

Re: 500 page while Authorize gitlab-ci

On Monday 26 January 2015 18:50:02 Markus Koeberl wrote: > Today I updated my Gilab server to the newest Debian omnibus package. Now I > am not able to get the omniouth login working for the ci server. But the > automatic build for previously configured repository is still working. &