CD

It’s hard to find terms getting more attention in the software world in the last few years than the closely related practices of Continuous Integration(CI) andContinuous Delivery or Continuous Deployment(CD), often referred to in tandem as CI/CD. Organizations across the world, from one-person development shops to multinational corporations, are implementing CI and CD for their software products.

We introduced improvements to pipelines to help scale applications and their repo structures more effectively. Here's how they work.

Orchestrating an application in Kubernetes can be even in a simple setup pretty complex. In this post, you learn how to architect a Kubernetes-native application and create a first deployment using kubectl.

Continuous delivery helps software development teams get their code changes from development to testing, and into the hands of users more quickly. In this post, Chris Ward looks at the benefits and best practices for implementing this practice into your teams.

Despite sounding similar, continuous integration, delivery, and deployment are subtly different from each other. While they have overlap, they are applicable and useful at different stages of the development process. In this post, we look at what the different terms mean, what benefits they bring to you and your team, and what you need to get started implementing the practice.