In this video, discover CI/CD tools and tool categories, including: self-hosted, SaaS, cloud service providers, and code repositories.
- [Instructor] With plenty of CI CD tools to choose from, we won't be able to explore all of them. But we can start narrowing our focus a bit by sorting tools into four categories. Self-hosted tools run on your hardware. This could mean the tool runs on a server in your company's data center, a VM in the cloud, or it could be on your local workstation. Whatever the platform you are responsible for installing the tool and maintaining it. Tools that fit into the software as a service or SaaS category, offer an alternative to self-hosting. In this case, a vendor provides and maintains the tool and allows you to access it. The next category is an extension of the software as a service category, cloud service providers offer SaaS-based CI CD tools but they also offer other cloud-based services like virtual machines, container registries, and cloud storage. If you think of a code repository, your first thought is probably of a place where you can store your code. But along with giving you a place to track and manage your code, many modern repositories also provide CI CD tools for turning that code into software. Now let's take a look at some of the pros and cons of tools in each of these categories.
- Key considerations in picking your stack
- The landscape of CI/CD tools
- Self-hosted options such as Jenkins and Bamboo
- SaaS tools such as Travis CI
- Using AWS CodePipeline and CodeBuild
- Tools for code repositories