Our Continuous Integration system is a panel that keeps track of our code repositories. For each of these repositories, you'll find what is commonly referred to as a job. A job is a series of steps, usually written in code, that informs the system of what it should do when a build is triggered through a button or CLI. A build is simply a single instance of that job that is running or has already run. Finally, that build contains log files, key information about the build, and any artifacts (objects) you want the system to store or ship off closer to the endpoint.
We'll build our CI system using Puppet, which will eventually manage our Puppet code. This is a common scenario when you start with CI in an existing environment in an organization.