Great! Thanks Gary!
On Jun 5, 2017 8:44 AM, "Gary Burchett" wrote:
> I just discovered that with this version that I recently updated to, the
> admin has the ability to set a default expire time for artifacts. I did not
> see this in the previous version I was running. The help for this admin
>
I just discovered that with this version that I recently updated to, the
admin has the ability to set a default expire time for artifacts. I did not
see this in the previous version I was running. The help for this admin
setting is located at
https://gitlab.com/help/user/admin_area/settings/con
I understand. Could you put it in your CI config files? That's where it's
meant to go. :)
See https://docs.gitlab.com/ee/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/gitl
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
See https://docs.gitlab.com/ee/ci/yaml/#artifacts-expire_in
"By default, artifacts are stored on GitLab forever."
So if you want to expire your artifacts, you have to set this value.
On Jun 2, 2017 7:27 AM, "Gary Burchett" wrote:
> Is there an gitlab.rb configuration option to set the default
