We often talk about Probo in regards to Drupal development because we do a lot of Drupal work at Zivtech. We originally built Probo to eliminate bottlenecks in our development workflow on our Drupal projects, but it can also be used to test any PHP and MySQL based application like WordPress or any other LAMP based CMS platforms.
Welcome to the Probo CI Blog!
Acquia BLT is an open source project that aims to provide pre-configured tools and tests for Drupal 8 projects, and it now has built-in support for Probo.CI. Out of the box Probo will:
From July 31st to August 2nd is the third annual Drupal GovCon, an awesome conference focusing on Drupal and Open Source Software in the government (mostly the U.S. Federal Government).
It's been about two years since we created Probo's initial UI designs. The UI and UX have served us well so far, but it's time for change!
The user experience for the app was originally developed mostly through intuition, like most brand new projects. We started off looking at other CI tools available, then modified what we found based on our needs.
We are excited to announce a couple new features for Probo customers this week: we now have 3 versions of our standard image to support various versions of PHP without having to run updates during the build process, and we now support .htaccess controls, to prevent unwanted viewing of your probo environments.
We've been adding new recipes to the Probo Documentation, and I wanted to share two that really speak to Probo's mission to enable Continuous Collaboration in software development projects: utilizing Backtrac.io for visual regression tests, and posting the Probo environment/sandbox and Backtrac.io test URLs into Jira.
I recently wrote a blog post on Medium titled Continuous Collaboration: Coining a new term for Probo, in which I describe the differences between Probo and other Continuous Integration software, and argue that we need a new term to describe software like Probo.