 Hey, I'm Andrew Connell. This video is an overview of one of the chapters in my course, Mastering the SharePoint Framework that's available for purchase on my site, boytanos.io. This overview video is going to give you an idea of everything that the chapter covers. You can learn more by checking out the description and the notes below the video. If you got any questions about this chapter or about the course in general, just make sure you drop a comment below the video and I'll be sure to get back to you. So with that, let me get out of the way. Enjoy the overview to this chapter. Development teams and organizations are always looking for ways to automate, streamline, and improve processes related to building software. SharePoint Framework development teams are really no different. This process usually brings together development and operations into a practice that's commonly called DevOps, and the idea is to continuously provide value to customers. And DevOps is comprised of many different practices and components. And one aspect of DevOps is continuous integration and continuous delivery, otherwise known as CI and CD. In this chapter, you're going to learn how to incorporate CI and CD practices into your SharePoint Framework projects using two very popular services, GitHub Actions and Azure Pipelines. So what exactly are we going to cover in this module? I'm going to start out with a brief introduction on what is DevOps, and we're not going to go too deep into this, but we need to have kind of like a full landscape to see the piece that we're going to be looking at. And that specifically is continuous integration and continuous delivery. That's the one aspect that we're going to focus on in this chapter. The SharePoint Framework also can take advantage of continuous integration and continuous delivery in practices in your projects. Now, we're going to look and see what that means in a SharePoint Framework project before we go about implementing it. And then we're going to go into two different directions. I'm going to show you two different ways that you can take advantage of CI and CD practices inside your SharePoint Framework projects. One way is using GitHub Actions, and we're going to talk about what GitHub Actions are, how they work, and the main components to it. And then we're going to see how we can go about in a demo in taking an existing SharePoint Framework project that we have built previously in the class that's filled with unit tests and React components and such like that. And we're going to see how to package up that project, to bundle it, to build everything, generate the SharePoint Framework artifact package that we need for deployment. We're also going to see how to run all of our tests. And assuming all of that stuff works and is still green, I'm then going to show you how we can go about deploying it, but not just deploying it to one environment. We're going to see how we can deploy it based on different conditions into different environments like dev or staging or even production if you wanted to have an automated rollout to production. Now, after we look at GitHub Actions, we're going to then pivot and we're going to look at how to do the exact same thing using Azure DevOps and a specific piece of Azure DevOps called multi-stage pipelines. Now, we're going to go through the exact same process that we go through with GitHub Actions. We're going to see in Azure Pipelines what are Azure Pipelines all about, what are the high-level components that DevOps and Azure Pipelines are going to give us. And then we're going to dive into a demo and take that exact same project and we're going to implement the exact same scenario that we did with GitHub Actions. We're going to do that same thing and implement it with Azure Pipelines. Now, I want to quickly have a word about context before we go too deep into this chapter. Most of the stuff that we're going to cover here is applicable to really all SharePoint. SharePoint 2016, SharePoint 2019, SharePoint Online. But I'm not going to focus or really spend too much time on the SharePoint Online story here. The two pieces that we are going to be able to automate is the build and the testing part, but we won't be able to do the deployment stuff on SharePoint 2016. There are no APIs for doing deployment on SharePoint 2016, so we can't automate it. SharePoint 2019 does have the ability to do that. But we're not going to focus on that. We're going to focus on SharePoint Online. And furthermore, we're really going to only focus on the online version of these services like GitHub Actions and Azure DevOps and Azure Pipelines. There are on-prem installs for some of these different products that have varying degrees of capabilities, but we're not going to focus on those. This chapter is going to be all about the online experience. I'm going to focus on SharePoint Online. I'm going to focus on GitHub Actions that is inside the hosted implementation of GitHub. And I'm going to focus on Azure DevOps Pipelines, which is in the Azure DevOps services, the hosted version of Azure DevOps. We're not going to look at the on-prem stuff. So it's not that you can't do that stuff. It's just that every single on-prem scenario is so very unique and so very different that it's just impossible to cover it in any amount of depth. But you should be able to take what you learn here and apply it to the on-prem story if that's what your situation entails. So let's dive into the first section and talking about implementing DevOps specifically continuous integration and continuous delivery with SharePoint Framework projects.