Automatic Build Cleanup in Probo.CI

We keeps your build environments running as long as possible so your team has time to review and test. But every build takes up storage, and every plan has a storage limit. To make sure you always have room for new builds, Probo.CI automatically cleans up older environments when your organization gets close to its limit. This process is managed by, what we call, the Reaper.

1. When Does the Reaper Run?

   The Reaper checks your storage usage every time a build finishes. If your organization’s total storage is within its limit, nothing happens - your builds are left exactly as they are.

   If your storage is over the limit, the Reaper steps in and removes older build environments until you’re back within your allowance. It only removes as many builds as necessary to bring your usage back under the limit.

2. Which Builds Get Removed First?

   The Reaper is designed to protect the builds your team is most likely still using:

   • Older builds go first. The Reaper always removes the oldest build environments before touching newer ones.
   • Pinned builds are never removed. If you’ve pinned a build, the Reaper will skip it entirely. Pinning is the way to tell Probo.CI “this one matters - keep it.”

   
   

3. Pinning a Build to Protect It

   If there’s a build your team needs to keep around - a version a client is reviewing, a release candidate, or something you’re actively debugging - you can pin it from the build page in the portal.

   Pinned builds are completely exempt from automatic cleanup. They will stay up until you unpin them or delete them manually.

   Keep in mind that pinned builds still count toward your organization’s storage usage. If you pin a lot of builds and your storage fills up, the Reaper will have fewer builds to choose from and may remove environments your team was still using. Unpin builds once they’re no longer needed to keep things running smoothly.

4. What Happens When a Build Is Removed?

   When the Reaper removes a build, the live environment is shut down and the storage it was using is freed up. The build’s history - the commit it was based on, which steps ran, and whether it passed or failed - is also removed.

   Removed builds cannot be restored, but you can always trigger a new build from the same commit if you need the environment back.

5. How to Avoid Unexpected Cleanup

   The best way to ensure the builds your team cares about stay available is to:

   • Pin important builds before your storage gets full. Don’t wait - if the Reaper runs before you pin a build, it may already be gone.
   • Delete builds you no longer need manually to free up space and give the Reaper more room to work with.
   • Upgrade your plan if your team regularly runs into storage limits. More storage means more builds stay active for longer. Visit our pricing page or contact us at hello@probo.ci to find the right plan for your team.

   
   

6. Questions

   If you have questions about build cleanup or your organization’s storage usage, please reach out to us at hello@probo.ci.