settings to cleanup artifacts when using omnibus distribution

2017-06-02 Thread Gary Burchett
Is there an gitlab.rb configuration option to set the default expires_in for artifacts in the omnibus releases (running 9.2.2 currently)? I could not find it in the documentation. This is a problem as the artifacts area has grown rather large and is adding substantial time to the backups. In th

Re: settings to cleanup artifacts when using omnibus distribution

2017-06-02 Thread Gary Burchett
I have read that page many times. In the omnibus distribution I need to be able to set this in /etc/gitlab/gitlab.rb file and not in the actual config files as they will be overwritten when I run gitlab-ctl reconfigure. I have tried looking in the code (to no avail) to see if I could find where

Re: settings to cleanup artifacts when using omnibus distribution

2017-06-05 Thread Gary Burchett
ci/yaml/#gitlab-ci-yml > > On Jun 2, 2017 2:33 PM, "Gary Burchett" > > wrote: > > I have read that page many times. In the omnibus distribution I need to be > able to set this in /etc/gitlab/gitlab.rb file and not in the actual config > files as they will

renaming project paths with new restricted/reserved names

2017-06-05 Thread Gary Burchett
I am running gitlab-ce 9.2.2 Omnibus distribution. My gitlab site has numerous projects that when created were permitted, but with newer versions of gitlab, now contain restricted/reserved path elements. eg foo/builds.git . How can I rename these projects? I cannot access their settings, even

using the V3 API to list public projects

2014-03-21 Thread Gary Burchett
When using the V3 API, the GET /projects does not appear to be returning public projects that I am not a member. Is this behavior expected? As admin I can see these by using GET /projects/all, This is not available to non-admin users. Is there a setting which controls if public projects are ret

Re: gitlab-rake gitlab:backup:create is not working

2014-07-03 Thread Gary Burchett
You probably have a error in your gitlab/config/gitlab.yml file. In the backup: section of this file, make sure that path: and keep_time: are aligned. If you just delete the '#' in front of the keep_time: line, you will end up with an extra space that can cause the error you are getting. The li

Re: gitlab-rake gitlab:backup:create is not working

2014-07-04 Thread Gary Burchett
Steven > > 在 2014年7月3日星期四UTC+8下午9时22分22秒,Gary Burchett写道: >> >> You probably have a error in your gitlab/config/gitlab.yml file. In the >> backup: section of this file, make sure that path: and keep_time: are >> aligned. If you just delete the '#' in fron

Re: gitlab-rake gitlab:backup:create is not working

2014-07-04 Thread Gary Burchett
Yes to both. The backup task will delete backups that are older than keep_time seconds. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegr