Build Pages



Search Results

Once your repositories are synced and you have begun using Probo, you can view all the Probo builds for each project. Each build page shows the list of the steps that were run, the log output for each step, and a link to the build itself.

Starting a Build from a Commit

To build from a branch:

  1. Navigate to your project in the Probo portal.
  2. Select the branch you want to build from the branch list.
  3. You will see the builds for that branch organized by commit. Select the commit you want to build.
  4. Click Build this commit.

Probo will apply the .probo.yaml in the commit specified. Once the build completes, you’ll receive a unique URL you can share or review.

Note: Manually triggered builds from commit hashes consume the same resources as Pull Request-triggered builds. They are subject to your account’s disc space limits and can be managed-pinned, rebuilt, or deleted-just like any other build.

Build Controls

Rebuild

The rebuild process deletes the existing environment and builds an entirely new one based on the same commit. If your site uses a database, the new build will receive a fresh copy of the database asset specified in the configuration file.

Pin

You can tell the Reaper a build is important by pinning it.

  • A pinned build will not be deleted when a new environment is built after a commit is pushed to its branch.
  • A pinned build will not be deleted when its pull request is closed.
  • If possible, a pinned build will not be reaped if you exceed your allotted disc space.

Note: When the Reaper is dispatched, it will reap all non-pinned builds before considering a pinned build eligible for deletion. If after all non-pinned builds are reaped and your account still exceeds its disc space, pinned builds become eligible and will be deleted from oldest to newest until you are back under.

Delete

You can manually delete unwanted builds to free up disc space for your account. Deleting a build completely removes its container from disc. You will be unable to rebuild the environment, but a change to the same Pull Request will build a new environment.

Deleting a build does not delete the build’s logs. Logs are still available on the build page, which can be found by showing all builds on the project page.

Advanced Functions

Following any of the advanced function links will open a terminal session in the build’s container directly in your browser. The SSH Terminal option gives you a full interactive shell, while the other options act as shortcuts to commonly accessed logs. If the build’s container has been stopped, opening any of these links will start it back up.

SSH Terminal

The SSH Terminal opens an interactive bash shell inside the build’s container, starting at the root directory. You have the same access as your build steps, so you can run the same commands you use in your .probo.yaml file - drush, composer, mysql and anything else installed in the container - to triage a failed step or inspect the state of the environment. This is the fastest way to debug a build: try commands interactively until they work, then move the fix into your .probo.yaml file. Even if a build step fails, you can go into the shell on the build or try to view it via the permalink link in the navigation.

Changes made in the shell affect the live build environment, so anything you change is reflected immediately at the build’s URL.

Log Tools

The remaining links each open a terminal that tails a specific log from inside the container, showing the most recent entries:

LOGWHAT IT SHOWS
Apache Access LogEvery HTTP request made to the build environment.
Apache Error LogWeb server errors, including PHP fatal errors that reach Apache.
Get Started with Probo.CI

Want to Try Probo today?
Get Started Fast!.

When you sign up for a Probo.CI registration code, you will get a two week trial of the plan of your choosing. For more information on how to get started, click here .

LEARN MORE ABOUT PROBO.CI'S PRICING