In this chapter, we focused on building out a CI System (Jenkins) and performing a validation check, a unit test, and an acceptance test. CI/CD is a continual journey, and there is always room for improvement in our workflows. Continuous Integration provides us with a valuable safety net for development, allowing us to develop without worrying about feature loss or regression. 

Where are some places to go to from here? Integrate your Git system closer to Jenkins by using Git hooks to deploy code, and providing a status back before a pull request is added. You can also add notifications to developers, alerting them when their tests have gone from passing to failing. If you find some of these warnings to be too much, tune the system providing the warning to avoid some of these errors. Everyone has a different CI/CD journey, so explore for yourself and figure out what works for you!

The next chapter covers Puppet Tasks and Puppet Discovery. Puppet Tasks allows us to run ad-hoc commands and use them as building blocks for imperative scripts. We'll be building a task to inspect log files and planning to build an aggregated log file for our Puppet Master. Puppet Discovery allows us to inspect our existing infrastructure and determine ground truth on packages, services, users, and various other components of a virtual machine or container.