In this first video of the course, you’ll get an overview about the courses content as well as a basic definition of Continuous Integration (CI). During this course you will work with Python as programming language and CircleCI as CI platform.
Hint: You can adjust the default video playback speed in your account settings.
Hint: You can set your subtitle preferences in your account settings.
Sorry! Looks like there’s an issue with video playback 🙁 This might be due to a temporary outage or because of a configuration issue with your browser. Please refer to our video player troubleshooting guide for assistance.
Intro to Continuous Integration
00:00 Hello, and welcome to the Real Python guide to Continuous Integration with Python. In this set of videos, you’re going to learn the core concepts and benefits behind continuous integration. Next, you’ll set up your own continuous integration pipeline.
00:15 And finally, you’ll use that continuous integration pipeline to manage a Python project. So, what is continuous integration, or CI? Continuous integration is the practice of frequently building and testing every change done to a piece of code, and then integrating that code as often as possible. In the past, changes were often built weeks apart, causing huge headaches and wasted time when it came time to merge.
00:39 Frequent builds means that any issues that arise can be traced back quickly and efficiently. CI also involves all developers on a project working on the same repository of code. While different teams and individuals may be on different branches of a repo, they’re all working off the same master. This way, as changes are added, all teams have access right away and can see how their code interacts with it.
01:02 Git is a common version control system, and you’ll be using GitHub later on for the example. A big piece of a CI pipeline is automating building and testing. Since Python is interpreted and doesn’t need to be compiled, we’re more concerned about the testing aspect, but you can think of the build as pulling all the required dependencies for the project. When testing is added to the CI pipeline, you can ensure that a successful commit passes all defined tests, even if the developer forgot to run the test locally.
01:31 External services are often used to handle CI pipelines, as this eliminates any specific conditions on an individual machine. In the examples section, you’re going to learn how to use CircleCI, which monitors a GitHub repo for changes and then builds the project based on a configuration file that you provide.
01:49 If this seems like a lot to take in, don’t worry. In the next section, you’re going to set up your own continuous integration pipeline and things should become clearer. So, let’s get started!
Become a Member to join the conversation.