Release Management
Articles
5 Tips to Take Your DevOps Pipeline Beyond the Basics The goal of a DevOps pipeline is to create a continuous workflow that includes the entire application lifecycle. But too often, people focus only on the tools and automating everything, not stopping to think whether their processes could further improve performance and efficiency. Let's look at some common challenges to continuous delivery and then learn five tips for refining your DevOps pipeline and taking it to the next level. |
||
Using Kubernetes for Container Orchestration in DevOps Containerization has replaced virtual machines to a great extent because containers are lightweight and make efficient use of the OS kernel. Docker’s efficient nature helps with software development, testing, delivery, and deployment in a DevOps environment, and all the benefits of Docker also apply to Kubernetes. Let’s explore some of the additional agile and DevOps benefits you can gain by using Kubernetes. |
||
Focus on Agile Engineering Methods in Your Digital Transformation Organizations undergoing a digital transformation must adopt new and meaningful ways of working. For a successful transformation, in addition to agile processes, teams must also leverage agile engineering techniques and models. Continuous focus on agile engineering principles will provide a solid ground for teams to enhance their agility and deliver better software, faster. |
||
DevSecOps: Incorporate Security into DevOps to Reduce Software Risk DevSecOps is a growing movement to incorporate security into DevOps practices in order to ensure flaws and weaknesses are exposed early on through monitoring, assessment, and analysis, so remediation can be implemented far earlier than traditional efforts. By failing fast with security testing, organizations reduce risk of a security incident and decrease the cost of rework. |
||
Why DevOps Still Needs Release Management 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. |
||
Has Continuous Deployment Become a New Worst Practice? Software development has been moving toward progressively smaller and faster development cycles, and continuous integration and continuous deployment are compressing delivery times even further. But is this actually good for businesses or their users? Just because you can deploy to production quickly and frequently, should you? |
||
Fixing a Broken Deployment Process When you have hundreds of applications performing various functions across several environments, it's tough to push all the code when it needs to be. Here are some steps to help your own team develop the internal tooling it requires to deploy thousands of applications if needed, all in a reliable, efficient manner. |
||
Test Coverage in the Age of Continuous Delivery Test coverage is a strategy to help us spend scarce testing time on the right priorities. When things were tested last, how much automation coverage we have, how often the customers use the feature, and how critical the feature is to application are all factors to consider. Here are some ideas for keeping quality high when you're transitioning to continuous delivery. |
||
Leverage Containers to Create Simulated Test Environments on Demand Adopting service virtualization can allow organizations to achieve more effective software development and testing by removing traditional test environment bottlenecks. Integrating service virtualization within the continuous delivery pipeline using containerization helps teams reach the level of flexibility required by today's competitive markets. |
||
Teach DevOps Software Development with a Game 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. |