Archives for the tag: deploy automation

This is the second in our five-part series from guest blogger J. Paul Reed—build engineer, automation enthusiast, and host of The Ship Show podcast. Jez Humble, author of Continuous Delivery and one of its founding fathers, has an informal survey he likes to give to audiences. It starts with a simple question: "Raise your hand if you do continuous integration." A sea of hands always rise. Then he says "Put them down if all of the developers on your team don't check into the main code-line

Continue reading »

This is the first post in our five-part series from guest blogger J. Paul Reed – build engineer, automation enthusiast, and host of The Ship Show podcast. Software development is moving towards continuity. The recent emphasis on continuous integration, built-in testing, constant monitoring, and feedback telemetry all point toward an overall trend in the software industry: increasing the ability to react. To become real-time businesses. As organizations explore what these changes mean for them,

Continue reading »

Your 2013 Continuous Delivery Resolution Just Got Easier

This is a guest post by Krishnan Badrinarayanan - product marketing manager for LiveRebel. A Java geek turned product marketer, Krishnan is well versed with issues that plague IT teams and is passionate about applying technology to solve their challenges. As a SaaS vendor, provider of online apps, or online retailer you already understand how important, although challenging, it is to meet constantly evolving user needs, and offer around-the-clock, worldwide availability. This especially holds true

Continue reading »

 9:00 am - Ahh, release day. You've run your test suite with each commit, and a green build has soaked on Staging for two days. Your application relies on a 3rd-party system to process credit card transactions - a critical dependency for your revenue stream. Your team didn't make any changes during soak time, but you don't know whether your credit card processing provider did. Worried? Nah, not you. You use multiple build triggers to run your tests with each commit, as well as nightly. So

Continue reading »