The principle “build once, deploy anywhere” is a fundamental part of Continuous Delivery and Deployment. If your underlying architecture is not built to support this behavior, you’re creating quite a few headaches for yourself and your Continuous Integration/Continuous Delivery/Deployment (CI/CD) pipeline. By following a few guidelines, you can ensure that the Artifact (the built code) you create is the same throughout each environment. In this article, we walk through a CI/CD pipeline deploying to AWS Elastic Container Service for Kubernetes (EKS) that simplifies the deployment process and guarantees the “build once, deploy anywhere” principle is followed.
Azure Builds & Azure Pipelines, part of the Azure DevOps Services suite, provide a Continuous Integration and Continuous Deployment/Delivery framework that you can get started with right away. This article looks at different approaches for handling Continuous Deployment across multiple environments so that you ensure a successful journey towards Continuous Delivery.
If you already have Jenkins as your build server and want to take advantage of services in Azure DevOps without fully switching over, you may find yourself with an existing Jenkins infrastructure, a source control repository, an Azure DevOps subscription, and a lot of questions. Fortunately, there are many extensibility points you can use to tie these solutions together in a way that works best for your business and team’s skillsets.
Recently, I had the pleasure of attending the 2018 DevOps Enterprise Summit (DOES) in Las Vegas. While conferences tend to make me fearful of getting sucked into a big sales show, DOES restored my faith (in the value of conferences, not Vegas!). Notably, it was extremely well-attended, impeccably run, and there was an elite cast of speakers throughout the event. From large talks to small group sessions to book signings, the event offered seemingly endless opportunities for interactive education.
Though a consistent definition of DevOps can be hard to come by, one thing we can all agree on is that the goal is to improve software delivery performance. While the desired outcome is clear, the path to achieving it is a bit hazy. As a practitioner of EOS, the Entrepreneurial Operating System developed by Gino Wickman, Author of Traction, Get a Grip on Your Business, we’ve realized the value that a scorecard adds towards identifying and measuring the key actions that will make our vision reality.
In this article, we provide an overview of the scorecard tool and outline some ways it helps us deliver 99.99 software.