The purpose of CI/CD security goes beyond identifying and remediating vulnerabilities—it also emphasizes keeping pace with other CI/CD processes. A secure CI/CD pipeline allows teams to find and fix issues without disrupting the overall CI/CD flow, achieving security without delaying or rolling back software releases.
Release management is still critical in a DevOps environment. You likely will just have to change your current process. You will no longer need to track implementation or back-out plans as part of change orders; you just need to be able to track the application, its components, and its promotion schedule. The key to maintaining these change orders is automation.
The core idea of DevOps is the various roles working together to create a stable software system. People can hear that, or read about it, or even observe it, but often, the best way for a team new to DevOps to understand it is to just do it. When you're starting out, that can lead to failures on a real system, so a simulation is a good idea. Try playing a game to introduce your team to DevOps.
Balancing time-to-market pressures with regulatory needs and business continuity demands is a challenge for highly regulated large enterprises. Automating processes and mastering proven practices of release management makes developing and releasing software predictable, reliable, and repeatable.
As software applications become more powerful and complex, users are demanding seamless and automatic updates. There is nothing worse than a “bricked system” after a failed update. The selection of a reliable file system is a vital component of the software update process.
High-stress situations arise when you have to respond to management's never-ending tough questions regarding product delivery. According to Johanna Rothman, you can properly set expectations without stress simply by understanding your manager's point of view.
Finding defects late is a common issue when teams don't consider levels of precision or detail. You must take into account how stories and features fit into the system. In this FAQ column, Janet Gregory tells you how you should remember the big picture—even while testing the small stuff.
In this interview, Ship.io general manager Prathap Dendi explores continuous delivery and the explosion of mobile development. He explains how we've applied the lessons learned from mobile development elsewhere, plus the most exciting trends now and looking forward.
In this interview, Matthew Bissett, the test manager responsible for the integration and testing of his area's flagship system for Her Majesty's Government, shares his thoughts with us on the importance of early testing in order to rapidly speed up software releases.
Agile DevOps focuses on moving changes through the pipeline as quickly as possible, which means that more operational tasks—like software deployment—will occur earlier. As a result, testing teams will begin assuming more responsibility in managing those deployments in order to perfect reputability. Tracy Ragan provides an overview of release automation as it relates to testing and explains how automation is key to achieving faster and leaner testing cycles. She discusses why deploying new code across diverse environments can be really tricky and slow, and how properly implemented release automation will streamline code deployments across the lifecycle. Release automation may sound like a topic important to production control teams, but as processes are shifted left, testing teams will take on more responsibility in continuous deployment and associated infrastructure components.
Committed to covering the latest trends and approaches for anyone investigating or implementing agile development practices, processes, technologies, and leadership principles, Agile Development & Better Software Conference West offers their 2013 interview series.
Picture this scene from three years ago: Employing the corporately mandated processes, a software engineering team is delivering system updates about once every nine months. When their senior user suddenly demands the next delivery in twenty-two weeks-half the current cycle duration-the team realize that they must quickly change development practices. Mathew Bissett describes how Her Majesty's Government did precisely that-and much, much more. First, they reduced delivery cycles from unpredictable dates every nine months to predictable releases every six weeks. Then, they cut releases cycle time to once every week. By identifying and mitigating risks early in the work intake process, enforcing quality gates, executing multiple test levels concurrently-and more-they dramatically increased throughput with the same or better quality. Today, these new processes provide their teams the best balance of structure versus agility.
The cloud is penetrating every technology organization and almost every software product or service. The cloud affects everything inside development, bringing profound changes to how engineers build, test, release, and maintain software and systems.