The Reaper Sharpens Up

By: Michael R. Bagnall

Last Updated: November 6, 2026

Reaper Quota Fixes, Reap Priority Established

If your organization has been sitting well above its disk allowance for a while without anything being cleaned up, this post explains why, what we changed, and what you will see from now on.

What changed

We have re-written the policy for which builds go first when an organization is over its limit:

1. Hash and branch builds first, oldest first. These are builds triggered from a commit on the project page or by a push to a branch. Nothing ever closes them, so they accumulate until something removes them.
2. Pull request builds only if that is not enough, oldest first. A pull request build already has a natural end: it is removed when the pull request closes or merges.
3. Pinned builds are never removed by the quota. Pinning has always meant “keep this”, and the disk limit now respects it fully.

The reaper removes as many builds as it needs to get the organization under its limit in one pass, and logs how many of each kind it chose. If every unpinned build is gone and the organization is still over, you will be unable to complete new builds.

What this means for you

If your organization is over its limit today, expect cleanup to begin the next time one of your builds finishes. Your oldest hash and branch builds will go first. Your pull request environments stay until the hash and branch builds are exhausted, which for most organizations means they are not touched at all.

If there is a hash or branch build you need to keep, pin it. Pinned builds are exempt from the disk limit and from the build-count limits. The usage figure on your organization page has been accurate throughout; it was the enforcement, not the measurement, that was broken.

Related Articles & Information

---

Updates to Disc Space Quotas and Asset Storage and The Reaper