{"id":21020,"date":"2019-09-10T12:10:10","date_gmt":"2019-09-10T11:10:10","guid":{"rendered":"https:\/\/www.devopsonline.co.uk\/?p=21020"},"modified":"2019-09-10T12:10:10","modified_gmt":"2019-09-10T11:10:10","slug":"continuous-delivery-in-devops-making-releases-dull-and-reliable","status":"publish","type":"post","link":"https:\/\/devopsnews.online\/continuous-delivery-in-devops-making-releases-dull-and-reliable\/","title":{"rendered":"Continuous delivery in DevOps: making releases dull and reliable"},"content":{"rendered":"
Continuous delivery in DevOps: making releases dull and reliable<\/em><\/p>\n There is some healthy tension between a good DevOps team and the concept of continuous delivery. In the past, a simple agile team would build products and let the delivery manager worry about what happens in production. With the coming together of Dev and Ops, as the portmanteau term suggests, things are different.<\/p>\n The more operationally minded engineers will look closely at the performance of the product in the live environment and push back on design assumptions that are contradicted when real people use a service or product. A good DevOps team will always make clear the risks involved with breaking changes and try to strengthen the processes that mitigate these.<\/p>\n What we understand initially by continuous delivery is simply that the team no longer does traditional release planning, with many stories rolled into one fat release. These were nervous times for an enterprise as a release may have held many vital changes for stakeholders.<\/p>\n The risk of having to roll changes back in case of problems would weigh heavily as the operations team carefully deployed the build overnight. With so many changes being deployed at once, problems were almost guaranteed over the following days.<\/p>\n With the increasing ways to make progressive releases, this form of software delivery life cycle (SDLC) is no longer favoured; now teams aim at regular small releases. This helps with pleasing customers quicker, as well as issue response being managed much more rapidly too.<\/p>\n The DevOps team is the key to this – the conveyer belt no longer stops at the delivery manager but goes all the way to the customer. Smarter use of observability and monitoring helps the team see how a live product is actually used, helping to predict what is likely to be needed in the near future.<\/p>\nThe story of the fat release<\/h4>\n