Jenkins is one of the oldest and most common Continuous Integration systems fielded today. It began as Hudson initially, in 2005, and grew into the fork of Jenkins that we see today. Jenkins is both a powerful and complicated system in comparison to most other CI systems due to its highly pluggable nature. There are a plethora of Jenkins plugins designed to add features to the CI system, from source code management, to graphs and viewing, to orchestration and automated testing and linting for nearly every language. With this wide feature set, Jenkins can also often be complicated. Out of the box, Jenkins doesn't do a whole lot outside of running shell commands on the system. In this section, we'll be exploring how to build a bare basic Jenkins setup for our needs, using Puppet, to manage our Puppet code.