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.
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.
What does it actually mean to get a link? Probo is unique because it actually spins up a whole new copy of your site that incorporates the proposed changes, and it gives you a link to see the version of the site with just that change.
Howard Tyson, Vice President of Engineering at Zivtech, recently gave a talk at DrupalCon Barcelona about Probo.CI, our new continuous integration tool that’s currently in beta. If you’d like a demo or to participate in the Probo.CI beta, hit us up at firstname.lastname@example.org.
As a project manager, you want to share a link with a client for quick feedback, and too often it‘s not as easy as it should be. Here’s the problem: you pass on a test link, and you throw in a caveat with very specific instructions: only test this feature and don’t touch anything else because there may be unfinished and unstable code in there.