How to Get CI/CD Right in 2021: A Guide to CI and CD

Rate this content

Software delivery is a top priority for organizations that own software, yet it remains one of the most challenging problems enterprises face today. Continuous integration (CI) and continuous delivery (CD) are software practices that allow organizations and teams to deliver code to customers quickly, safely, and repeatedly. Whether it's to improve development, operations, or security, CI/CD pipelines give engineers and teams more time to work on things that matter and less time struggling with the risk, standards, and velocity of deployments. Join this session to learn about the components of CI/CD and how to build and scale pipelines for the future.

9 min
01 Jul, 2021

AI Generated Video Summary

This talk provides an introduction to CI/CD, discussing its key components and how to succeed with it. It emphasizes the importance of speed, safety, and scaling in CI/CD, highlighting the need for unit tests, value stream management, metrics, and addressing deployment challenges. The talk also emphasizes the continuous nature of DevOps and the importance of gathering feedback and releasing changes to a subset of users.

1. Introduction to CI/CD

Short description:

Hi, everyone. Thanks so much for joining this session on CI/CD. I'm Tiffany Jackja, a technical evangelist at Harness. We'll discuss the key components of CI/CD and how to succeed with it. CI/CD is the heart of continuous integration and continuous delivery, enabling quick and safe deployment of changes. It involves a pipeline that automates processes in the software development lifecycle. The pipeline includes continuous integration, focusing on the development workflow, and continuous delivery, provisioning the infrastructure for production. The goal is to get changes into the hands of users in a safe, quick, and repeatable way. By applying governance, secrets management, and security benefits, we can build a strong foundation for scaling services and working with different kinds of services.

Hi, everyone. Thanks so much for joining this session, a how to guide on CI CD. I'm Tiffany Jackja. I'm a technical evangelist at Harness. We help simplify and scale software delivery. I'm actually really excited to be sharing this presentation because I know for a lot of people looking into DevOps and you know making that journey better. CI CD comes up very often and so we're actually going to share some of the key components of CI CD and then we'll actually get into some of the ways that you can better succeed and position yourself for 2021.

So let's just get started. I know we don't have a lot of time in a lightning session but I really just want to share a very basic CI CD pipeline. And so when you think about CI CD pipelines and just the idea of a pipeline, you, it's really just this conduit for being able to automate some of these processes that we have in a software development lifecycle. So if you have an idea or a change to be made, we actually want to deliver that or put that into a pipeline that gets you to production.

And so that process can involve making some code changes, right? Building that code change, testing it and then deploying it into this temporary environment, it's non-production environment, where you can test it and play with it, right? And verify and make sure that it's ready before actually releasing it to a customer and having it be available to the outside world, right? And so this idea of getting from idea to production very quickly is the heart and sort of the soul of continuous integration and continuous delivery.

And so there are two main points to a CI CD pipeline, and you really do want to think about it in this way. So this first part is about continuous integration. And when we talk about continuous integration, we're actually trying to focus on that development workflow, getting from code to packaged artifact. And really what happens in a continuous integration process is you have some source code management tool, right, or repository of code. And whenever someone pushes a change or makes some type of change, you can actually trigger a CI pipeline where you get to build that application, ensure that it compiles, ensure that it has all the dependencies that you need, that you can run some very basic unit tests, some very cheap and fast tests to ensure that these changes can go through, right. And then once that happens, once it's packaged, right, you can actually version it and have it be available to run on a server. And that's when we actually talk about continuous delivery. That's when we talk about provisioning a server, right. Provisioning some infrastructure, ensuring that infrastructure has everything that it needs to run an application, right, whether it's like a database, or maybe it needs some setup, some administrator to manage it, right. And so in this continuous delivery aspect, we're trying to think about ways of releasing it into a production environment, delivering it there, not just having it run there, right. And so thinking about really strategies, thinking about verification and just in case things go wrong, strategy for rolling back issues. And so to even get to continuous delivery or this idea of whatever, continuous flow, even DevOps, really, we need to think about this ability to get all kinds of changes into the hands of users and not only just being able to do it once or twice, but actually being able to do it in a safe, quick and repeatable way. And this definition comes from Jez Humble, who wrote a book on continuous delivery. And so that's why today I think we're starting to see a larger ecosystem around CI and CD, right, this idea that we can apply governance to our CI-CD pipelines, we can apply secrets management, security benefits, right, and actually build out a whole ecosystem around this, and have really good foundation for whatever we may want to do. Because the reality of it is that we have a lot to do, right, whenever we want to scale a new service or even just ensure that we can work with different kinds of services, sometimes this process can take weeks or even months, and the reality of it is we shouldn't be taking that long and eventually we'll be able to solve for a lot of these things with CI-CD.

And so, this gets to the latter part of my presentation about how to succeed with CI-CD and what are some key areas that you want to focus on. And so, I really kind of think about it in these three areas about speed, safety, repeatability, and users. And there's a lot of different ways that you can get better at this, right? It's not a one and done kind of deal, and you may, you know, invest in certain areas over others first.

2. Speed, Safety, and Scaling in CI/CD

Short description:

Maybe speed doesn't matter because you don't need to deploy every day. Consider having enough unit tests and building capabilities before investing in a perfect CI/CD pipeline. Value stream management helps eliminate idle time. Metrics measure speed and tempo. Safety ensures changes are problem-free and secure. Sustaining and scaling delivery requires visibility, standardized templates, and addressing deployment challenges. Gathering feedback and releasing changes to a subset of users are crucial. Remember, DevOps is a continuous process. Thank you for joining!

Maybe speed doesn't matter because you don't need to deploy every day. Then maybe you want to consider, do I have enough unit tests? Am I building enough capabilities in a particular area before I go and try to invest in all of these areas or try to have this perfect CICD pipeline when no one needs it yet, for example.

And so, some of the ways that you can start thinking about speed is through value stream management. So, this is eliminating any areas of just, you know, waiting idle time, basically. You know, if someone commits some code and it actually doesn't get packaged into an artifact a year, three years, that could impact how often you actually go to deploy.

And so, the second half right here, I have a couple of metrics that you can use to kind of measure speed and tempo. And I'm going to be sharing more metrics around this area. I do want to go a little quicker and also talk about safety. So, safety is about being able to ensure that all of our changes are, don't cause any problems and that they're secure. Things like the SolarWinds hack, that was a really big issue. Things like being able to understand your micro-services, your architectures, those are all really important as well.

And then there's this area of being able to sustain and scale out continuous delivery and software delivery. And so, it's thinking about, well, do I have enough visibility into all of my processes? Do I have pipeline templates, standardized templates that have been proven out that I can just repeat around? And, you know, how do people feel about this? Are they burnt out every single deployment? Does it take a village to deploy? All these things can be a really big challenge.

And then this final area that I want to get to, for this talk, is around your users, right? Being able to gather feedback, being able to also release changes to a subset of users before you go on. These are all really important aspects. And so, these are some areas that you can think about. I know that we're running out of time. I do want to say that if you are going to be thinking about DevOps and about CICD, just remember that, you know, this is a continuous process. And so, as we build out new processes, we can get better and improve on our processes and really, really do enable that DevOps lifecycle. So, I just wanted to say thank you so much for joining this session. If you have any questions, feel free to ask me. I'll be around.

Check out more articles and videos

We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

React Advanced Conference 2021React Advanced Conference 2021
19 min
Automating All the Code & Testing Things with GitHub Actions
Code tasks like linting and testing are critical pieces of a developer’s workflow that help keep us sane like preventing syntax or style issues and hardening our core business logic. We’ll talk about how we can use GitHub Actions to automate these tasks and help keep our projects running smoothly.
DevOps.js Conf 2022DevOps.js Conf 2022
33 min
Fine-tuning DevOps for People over Perfection
Demand for DevOps has increased in recent years as more organizations adopt cloud native technologies. Complexity has also increased and a "zero to hero" mentality leaves many people chasing perfection and FOMO. This session focusses instead on why maybe we shouldn't adopt a technology practice and how sometimes teams can achieve the same results prioritizing people over ops automation & controls. Let's look at amounts of and fine-tuning everything as code, pull requests, DevSecOps, Monitoring and more to prioritize developer well-being over optimization perfection. It can be a valid decision to deploy less and sleep better. And finally we'll examine how manual practice and discipline can be the key to superb products and experiences.
DevOps.js Conf 2022DevOps.js Conf 2022
27 min
Why is CI so Damn Slow?
We've all asked ourselves this while waiting an eternity for our CI job to finish. Slow CI not only wrecks developer productivity breaking our focus, it costs money in cloud computing fees, and wastes enormous amounts of electricity. Let’s take a dive into why this is the case and how we can solve it with better, faster tools.
DevOps.js Conf 2022DevOps.js Conf 2022
31 min
The Zen of Yarn
In the past years Yarn took a spot as one of the most common tools used to develop JavaScript projects, in no small part thanks to an opinionated set of guiding principles. But what are they? How do they apply to Yarn in practice? And just as important: how do they benefit you and your projects?
In this talk we won't dive into benchmarks or feature sets: instead, you'll learn how we approach Yarn’s development, how we explore new paths, how we keep our codebase healthy, and generally why we think Yarn will remain firmly set in our ecosystem for the years to come.
DevOps.js Conf 2024DevOps.js Conf 2024
25 min
End the Pain: Rethinking CI for Large Monorepos
Scaling large codebases, especially monorepos, can be a nightmare on Continuous Integration (CI) systems. The current landscape of CI tools leans towards being machine-oriented, low-level, and demanding in terms of maintenance. What's worse, they're often disassociated from the developer's actual needs and workflow.Why is CI a stumbling block? Because current CI systems are jacks-of-all-trades, with no specific understanding of your codebase. They can't take advantage of the context they operate in to offer optimizations.In this talk, we'll explore the future of CI, designed specifically for large codebases and monorepos. Imagine a CI system that understands the structure of your workspace, dynamically parallelizes tasks across machines using historical data, and does all of this with a minimal, high-level configuration. Let's rethink CI, making it smarter, more efficient, and aligned with developer needs.

Workshops on related topic

DevOps.js Conf 2022DevOps.js Conf 2022
152 min
MERN Stack Application Deployment in Kubernetes
Deploying and managing JavaScript applications in Kubernetes can get tricky. Especially when a database also has to be part of the deployment. MongoDB Atlas has made developers' lives much easier, however, how do you take a SaaS product and integrate it with your existing Kubernetes cluster? This is where the MongoDB Atlas Operator comes into play. In this workshop, the attendees will learn about how to create a MERN (MongoDB, Express, React, Node.js) application locally, and how to deploy everything into a Kubernetes cluster with the Atlas Operator.
DevOps.js Conf 2022DevOps.js Conf 2022
13 min
Azure Static Web Apps (SWA) with Azure DevOps
Azure Static Web Apps were launched earlier in 2021, and out of the box, they could integrate your existing repository and deploy your Static Web App from Azure DevOps. This workshop demonstrates how to publish an Azure Static Web App with Azure DevOps.
React Summit 2023React Summit 2023
88 min
Deploying React Native Apps in the Cloud
Deploying React Native apps manually on a local machine can be complex. The differences between Android and iOS require developers to use specific tools and processes for each platform, including hardware requirements for iOS. Manual deployments also make it difficult to manage signing credentials, environment configurations, track releases, and to collaborate as a team.
Appflow is the cloud mobile DevOps platform built by Ionic. Using a service like Appflow to build React Native apps not only provides access to powerful computing resources, it can simplify the deployment process by providing a centralized environment for managing and distributing your app to multiple platforms. This can save time and resources, enable collaboration, as well as improve the overall reliability and scalability of an app.
In this workshop, you’ll deploy a React Native application for delivery to Android and iOS test devices using Appflow. You’ll also learn the steps for publishing to Google Play and Apple App Stores. No previous experience with deploying native applications is required, and you’ll come away with a deeper understanding of the mobile deployment process and best practices for how to use a cloud mobile DevOps platform to ship quickly at scale.
DevOps.js Conf 2022DevOps.js Conf 2022
163 min
How to develop, build, and deploy Node.js microservices with Pulumi and Azure DevOps
The workshop gives a practical perspective of key principles needed to develop, build, and maintain a set of microservices in the Node.js stack. It covers specifics of creating isolated TypeScript services using the monorepo approach with lerna and yarn workspaces. The workshop includes an overview and a live exercise to create cloud environment with Pulumi framework and Azure services. The sessions fits the best developers who want to learn and practice build and deploy techniques using Azure stack and Pulumi for Node.js.