Controlling GitLab CI Artifact Expiration to Tame Storage Costs
GitLab CI artifacts accumulate by default, inflating repo size and slowing fetches. Learn how to set expiration via UI or YAML, handle version differences, and verify cleanup.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
GitLab CI artifacts accumulate by default, inflating repo size and slowing fetches. Learn how to set expiration via UI or YAML, handle version differences, and verify cleanup.
GitLab CI artifacts are kept forever unless you set artifacts: expire_in. Learn how to configure per-job retention, avoid common mistakes, and verify cleanup actually happens.
Learn how VMware’s Storage DRS auto‑balances I/O and capacity across datastore clusters, with a step‑by‑step setup, example migration, trade‑offs, and practical checks to keep your vSphere environment running smoothly.
Learn how to use RHEL Logical Volume Management (LVM) to expand storage online. This guide covers PV, VG, and LV configuration with specific commands for XFS and EXT4 filesystems.
Figma's auto-save mechanism continuously records cloud-stored snapshots of files as edits occur. For low-traffic workloads, this produces a persistent revision chain that expands over time even when activity is minimal, and there is no documented setting to disable auto-save or cap the number of retained revisions per file. Because storage and revision histo