As DevOps teams make progress in collaboration, automation and more, new services and functionality continue to emerge to help further streamline roles and processes. At DevOps World | Jenkins World last week, we saw several examples of this with attendees getting a preview of CloudBees’ Software Delivery Management (SDM) Platform along with its Product Hub and Value Stream Management modules; enhancements to the CloudBees Accelerator and much more.
We recently had the opportunity to work with a global communications company that shapes how consumers, businesses, governments and militaries around the world communicate. As part of our work with them, we were establishing a new AWS Disaster Recovery (DR) process, part of which had a Jenkins backup in another AWS Availability Zone (AZ). In helping the firm with its cross-AZ DR process, we were challenged with the Jenkins job status which impacted the AZ status. AWS Disaster Recovery blog is the story of how we approached the situation, creating a unique solution that solved the customer’s needs all in one place.
Recently Aater Suleman, Flux7’s CEO, presented an “An Introduction to DevOps with AWS: How to Design, Deploy, and Manage a DevOps Workflow in AWS” as part of the O’Reilly live, online training series. In it, he was asked this pivotal question from one of the attendees: What future-looking skills should sysadmins have to ensure long-term competitiveness in DevOps environments and we thought we’d share his answer here with you today.
Our clients are always deeply interested in creating productive dev environments. The power of a dev environment comes from many places. First is time saved by reducing the number of manual steps and by preventing context switches for a developer. Improving flow enables a developer to catch bugs sooner when they’re still inexpensive. Consequently, moving toward continuous testing and integration is essential. In this post, we’ll discuss a continuous integration workflow using opensource tools.