Probo.CI's New Beginning

By: Michael R. Bagnall

Last Updated: April 4, 2026

We have been busy. Since FlyingFlip Studios took the reins of Probo.CI, the team has been working hard across every part of the platform - from the portal you log into every day to the infrastructure running quietly behind the scenes. Here is a look at what has changed, what has improved, and what is coming next.

Smarter Builds

We have made several improvements to how builds are triggered and managed to cut down on noise and give your team a cleaner experience.

Bitbucket users will notice that builds no longer restart when a pull request is updated without any code changes - things like adding a reviewer or editing the PR description no longer waste a build slot. We have also fixed a bug where, in some cases, the wrong user’s credentials were being used when triggering builds. Both of these were longstanding pain points and we are glad to have them resolved.

GitLab users will find that this integration has also been modernized significantly under the hood, which means better reliability and a smaller footprint.

More Languages and Frameworks

Probo.CI now supports a wider range of technologies out of the box:

• Drupal 11/12 and Drupal CMS are now fully supported, including configuration import, Redis caching, and database sanitization steps.
• .NET builds are supported across versions 6 through 10 with dedicated container images.
• Node.js applications now have a dedicated plugin with configurable build commands and environment variables.
• Apache Solr versions 5 through 10 are supported for projects that rely on search infrastructure.
• Backdrop CMS now has a dedicated provisioning plugin.
• Python support is now avaiable.
• Database support has expanded to include MySQL 5.7, 8.0, and 8.4; MariaDB 10.11, 11.4, and 11.8; PostgreSQL; and SQL Server (MSSQL) - all with support for both gzipped and bzipped database imports.

If your stack was not quite supported before, there is a good chance it is now.

Build Environments That Stay Reliable

One of the things that makes Probo.CI different is that your build environments stay up after a build finishes, giving your whole team time to review. We have done significant work to make those environments more reliable.

Builds that were previously getting stuck in intermediate states - showing as running when they had actually finished - are now handled correctly. We have also improved how build cleanup works so that environments are removed cleanly when a pull request is closed, freeing up your storage automatically.

Asset Storage Improvements

The system that handles your uploaded assets - database dumps, environment files, and other build dependencies - has been significantly improved. It is now faster, more reliable under load, and handles duplicate file names more gracefully: uploading a new version of a file with the same name now cleanly replaces the old one rather than stacking up copies.

We have also added protections to prevent storage from being quietly consumed by oversized uploads, and improved the checks that ensure your organization’s subscription is in good standing before accepting new assets.

What Is Coming Next

This release represents a foundation. A new portal is on the way, but there is more to come - richer build views, improved organization management, and better visibility into your team’s activity across projects.

We are also continuing to expand language and framework support based on feedback from the community. If there is something you need that is not yet supported, reach out to us and let us know.

Thank you for being part of the Probo.CI community. We are excited about where this is going and glad to have you along for the ride.

Related Articles & Information

---

Environment Setup