settings to cleanup artifacts when using omnibus distribution

[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 the meantime I have manually cleaned up (aka deleted) a large amount of old artifacts.

[Aleksey Tsalolikhin]

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" <gary.b...@sas.com> wrote:

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 the meantime I have manually cleaned up (aka deleted) a large amount of old artifacts.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/94d326b1-e575-4e70-a17b-1e1b969bb5e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[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 expires_in would be set from the templates used to create the config files. Regardless, thank you for the reference.

On Friday, June 2, 2017 at 1:11:15 PM UTC-4, Aleksey Tsalolikhin wrote:

See https://docs.gitlab.com/ee/ci/yaml/#artifacts-expire_in

...

[Aleksey Tsalolikhin]

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

--

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+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/1e9c76c9-5403-47d5-8500-234b872008d5%40googlegroups.com.

[Gary Burchett]

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/continuous_integration#default-artifacts-expiration  I never did find this page when googling for this issue. This solves my issue. I think it would also be useful for the admin to be able to set a maximum expires values regardless what expires_in value a user sets in their project. Artifacts can grow substantially in a short amount of time.

Thank you for your help.

On Friday, June 2, 2017 at 6:48:00 PM UTC-4, Aleksey Tsalolikhin wrote:

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" <gary.b...@sas.com> 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 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 expires_in would be set from the templates used to create the config files. Regardless, thank you for the reference.

On Friday, June 2, 2017 at 1:11:15 PM UTC-4, Aleksey Tsalolikhin wrote:

See https://docs.gitlab.com/ee/ci/yaml/#artifacts-expire_in

...

--
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+u...@googlegroups.com.

[Aleksey Tsalolikhin]

Great! Thanks Gary!

To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/3ce6e6ef-b6b1-4ee5-9b29-c306be7bf9b4%40googlegroups.com.