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. 

We 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:

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.

Probo 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.

I'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, from UC Davis' web team, gave a great BADCamp 2016 Session: Drupal 8 Distribution Development and Devops Workflow.

Please note that the most up-to-date Probo Product Roadmap can now be found on the Probo Documentation site

Yesterday 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.

Not long ago we were talking about the value of testing your updates in feature branch instances. It’s the most efficient way of ensuring the quality of applied updates, but it’s very time-consuming.

To 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.

Continuous delivery, deployment, and integration tools are popping up in more places every day. Developers at Instagram recently wrote a blog post about the internal tool they built to allow the team to automate backend code deployment up to 50 times every day, “whenever engineers commit changes to master…with no human involvement in most cases.”