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.
New environment variables for builds
May 19, 2017We are excited to announce a few more environment variables available for you to use in Probo! There were several available before, and we've expanded that list to include:
Defining Probo's Mission & Coining Continuous Collaboration
May 18, 2017I 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.
WordPress on Probo
April 14, 2017Probo is built by Zivtech. We are mainly a Drupal shop, but Probo is not a Drupal-specific tool. We use it with any web technology, including WordPress.
One of our clients using WordPress is All Ages Productions, a video production company here in Philadelphia. All Ages created the Probo explainer video for us, and in return we help them support their WordPress site, so they got to experience the product they were helping us market as end-users.
New on Probo 12/16: Bitbucket Server/Stash, Improved Logs, Pinning/Deleting Builds, & More
December 16, 2016I'm proud to say that we recently made our Bitbucket Server integration (formerly known as Stash) available to everyone on Probo.Ci, the SaaS version of Probo. What does that mean? Well, it means that when you're logging into Probo.Ci there's now a new option:
Shawn Dearmond: Drupal 8 Distribution Development and Devops Workflow - BADCamp 2016
October 26, 2016Probo Roadmap
October 20, 2016Better Error Handling and More To Come!
October 7, 2016Yesterday we pushed a big release that gave us a lot of behind the scenes improvements and a few that will be very visible to our users. When you tried to visit a build that we removed because you pushed newer code or because you had exceeded your disk quota, we would serve you an internal error in JSON format. Some of our power users learned to know what those error codes meant but for most people it was disorienting and definitely didn't feel very polished.
Probo.CI and Drop Guard work together for a better QA process
May 19, 2016To use this process, you are required to maintain your own infrastructure to spin up QA servers quickly, run automated tests and share the testing instance between team members. And preferably, you do it every time an update is applied for any of the modules across your websites.