ProboCI ChangeLog

If it has been a while since you looked at Probo.CI, it is worth another look. Over the past year we widened what Probo can build, made builds faster to get to, and took the waiting out of the parts that used to cost your team time. Here is what changed.

Probo Builds More Than PHP Now

Probo started with Drupal and WordPress. It is not limited to them anymore. If your team has moved on to a different stack, or runs several at once, Probo covers it.

• Node.js applications have their own build type, so React, Next.js, and Node backends get a live preview per pull request just like everything else. See Node.js.
• Python applications are supported, with whatever Python version you ask for and your dependencies installed for you. See Python.
• .NET applications are supported across .NET 6 through 10, including projects backed by SQL Server. See .NET.
• Static sites build without the overhead of a database or an application server.
• Drupal 11 and Drupal CMS are fully supported, and Drupal 7 projects still build if you have not finished migrating. See Drupal.
• Backdrop CMS and Joomla joined the list of supported platforms. See Backdrop and Joomla.
• PHP 5.6 through 8.5 are all available, so a legacy client site and a modern one can live side by side in the same organization. See Supported Versions.

Previews That Match Production

The closer a preview is to your production environment, the more you can trust the feedback you get from it. Probo builds now mirror a much wider range of real stacks.

• Choose your database. MySQL, MariaDB, PostgreSQL, and Microsoft SQL Server are all available, in the versions your project actually runs. See Database Configuration.
• Load compressed database dumps directly. Gzipped and bzipped files import as they are, which means faster builds and less of your storage quota spent on unpacked copies. See Importing Databases.
• Search works in the preview. Apache Solr is a supported service now, with your version and your cores, populated from your data. See Solr Configuration.
• Caching behaves like production. Redis and memcached are available in every build. See Redis Configuration.
• Bring your own configuration. Drupal builds accept your configuration import, your settings files, and your database sanitization rules instead of forcing our defaults on you.

Get to the Build You Need

Not every review starts with a fresh pull request. Sometimes you need one specific change in front of a client this afternoon.

• Build any branch or any commit on demand. Pick it from a list in the portal and Probo builds it. No pull request required.
• Commit builds show the commit message, so you can tell at a glance which build is which.

No More Wondering What Your Build Is Doing

• Build output streams to your screen as it happens. Watch each step run and scroll along with it. No refreshing, no guessing whether anything is still moving. See Build Pages.
• Busy mornings queue instead of failing. When your team opens a dozen pull requests at once, the extras line up and start as capacity frees. See Build Queues.
• A configuration problem looks different from a failed test. Builds that never got off the ground are marked distinctly, so you know whether to fix your code or your setup.
• Builds that come up empty are caught. Probo verifies your application is genuinely responding rather than reporting success on an environment nobody can use.

Keep Secrets Out of Your Repository

• Set secrets on a project, or across an entire organization, from the portal. Probo passes them into the build without them ever living in your repository. See Variables and Secrets.
• One organization secret covers every project, and any single project can override it when it needs something different.

Better Asset Handling

• Upload and delete assets right in the portal. Database dumps and files no longer require a trip to the command line. See Assets.
• You can see your storage against your quota, with a heads up before you run out rather than after. See Quotas.

Fixes Worth Fussing Over

These are the fixes worth knowing about. They are the reason some teams had a bad week with Probo, and they are resolved.

• Merging or closing a pull request stops its build immediately and tears down the environment, instead of spending your capacity on work nobody is going to look at.
• Pinned builds stay pinned, and abandoned ones get cleaned up properly, so your quota reflects reality. See Automatic Build Cleanup.
• Every build serves over HTTPS, which matters for anything testing logins, payments, or third party embeds.

A Portal That Gets Out of Your Way

• A rebuilt dashboard puts your organizations, projects, and recent builds in one place. See Using the Portal.
• Open a support ticket from inside the portal, without switching to email and hoping it reaches someone. See Support.
• Manage who administers your organization yourself, from your account. See Manage Administrators.
• You are warned before you run out of storage, with a clear path to more if you need it.
• Service notices appear in the portal, so you hear about maintenance before it affects a build.

Billing That Respects Your Money

• Change plans and pay only the difference. Upgrades and downgrades are prorated and settled immediately instead of resetting your billing cycle. See Subscriptions.
• Cancel your plan yourself, from your account. No ticket, no waiting on us to process it.
• Your build resources scale with your plan. A larger subscription now means more processing power and memory in every container, not just more storage.

Come See for Yourself

If you stepped away from Probo.CI at some point, most of what sent you away has been rebuilt or removed. Finding out costs nothing.

Your first month is on us. Every new organization gets a full month free on any of our plans, with no payment information required to start. Connect a repository, point Probo at a real project, and see where it lands.

Get started or compare our plans to find the right fit for your team.