Summary

In this chapter, we came to the core of CI, automation. Using Gulp, we automated our build, linting, and testing. That is all very nice, but for now, it only works locally. You can still forget to run Gulp, or ignore it, and commit a broken build. In the next chapter, we are going to take a closer look at Jenkins. Jenkins, like Gulp, is all about automation. While Gulp and Jenkins are nothing alike, besides the fact that they both assist in automation, the most important difference is that Jenkins runs on a server and will check your commit even if you did not.