Projects in Probo.CI

A Probo.CI Project represents a single enabled repository. When you activate a repository, a Project is created for it automatically. The Project is the central record that ties together your builds, asset storage, branch configuration, and notifications for that repository.

1. Projects and Repositories

   A Project is not the same as a repository, but the two are tightly linked. A repository exists in your git hosting provider (GitHub, GitLab, Bitbucket); a Project is the corresponding Probo.CI record created when that repository is activated. Each repository maps to exactly one Project, and each Project belongs to exactly one Organization.

   When a repository is deactivated, its Project becomes inactive. Projects are not immediately deleted - they are soft-deleted, meaning their history is retained until permanently removed.

2. What a Project Contains

   A Project owns or tracks the following:

   • Builds - every build environment created for a pull request in the repository belongs to the project. Each build tracks its status, steps, branch, commit, pull request reference, and disc usage.
   • Branches - a per-branch configuration that controls which branches automatically trigger builds on push.
   • Asset bucket - each project is assigned a dedicated asset storage bucket for files uploaded via the asset receiver, such as database dumps or credential files.
   • Asset tokens - one or more upload tokens scoped to the project’s asset bucket. Tokens can be added or revoked as needed.

   
   

3. Disc Space Quotas

   Disc space is not limited at the project level. Storage quotas are applied at the organization level, covering the total disc used by all active build environments across every project in the organization.

   When an organization’s disc usage exceeds its subscription limit, the Reaper automatically removes older build environments to bring usage back within the limit. Pinned builds are never reaped.

   See Disc Space Quotas for full details on how the Reaper selects and removes builds.

4. Asset Storage Quotas

   Each project’s asset bucket is subject to a hard limit of 10 GB of compressed storage. This limit is enforced by the asset receiver independently of your subscription plan.

   When a bucket reaches 10 GB, further uploads won’t show in the list of assets. No automatic cleanup occurs - you must delete assets you no longer need before new uploads will be accepted.

   Uploading an asset with the same filename as an existing asset automatically replaces the previous version, which helps keep bucket usage manageable over time.

   See Asset Disc Space Quotas for full details.

5. Questions

   If you have questions about a project’s configuration, asset storage, or build history, please reach out to us at hello@probo.ci.