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.
Technology is ever-changing, and the options available to product teams continue to expand. Coordinating a team around a technology stack can be challenging, but it’s a necessary practice to enable faster delivery.
In this article, we’ll show you how we worked with one product delivery team to realize the benefits of adopting .Net Core and developed a template application that could be used for future development efforts.
Going cloud-native and choosing AWS as your cloud platform is an important decision. Once you’ve set your mind to that path, the next step is to select the right managed services for your infrastructure. If you’re implementing a microservice approach on AWS, there are multiple options for hosting your containerized services. Here is a high-level overview of ECS, Fargate, and EKS and tips for choosing the best container orchestration option for your organization.
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.