Skip to content

Enable performant artifact expiration by default

drew stachon requested to merge enable-expiration-by-default into master

What does this MR do and why?

This MR changes the default behavior of our safety-valve feature flags to true, to keep artifact expiration enabled on self-hosted instances. While we use some granular controls to increase the pace on gitlab.com, we need to make sure that self-hosted customers get the benefit of our improved code and expire up to 10k artifacts per execution these flags are combined with !77603 (merged)

This will not work on older expired artifacts, where the artifact locked value is unknown. Just newly expired artifacts that were created

The idea here is that by default, GitLab instances will not have a growing backlog of expired artifacts that cannot be removed. If an instance has a backlog of old artifacts, we're not touching those for now as we still need to sort out &7097. But in the mean time, we can increase the rate at which newly expired artifacts are removed, preventing anyone's problems from getting worse.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by drew stachon

Merge request reports