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 ...
