We have come pretty far. We have built a JavaScript application with Node.js and automated it with Gulp. We then did the same in C# and did all the work during the build. After that, we automated everything in Jenkins, so not a single commit is not tested and build. However, as far as Jenkins is concerned, we did the bare minimum to get our software to be tested and built.
Unfortunately, in a limited testing environment, such as ours, we do not run into the problems you are going to face in the real world. For example, we currently have two projects, JavaScript and C#, which together make up for six projects. In my daily job, we have, maybe, two hundred projects. Personally, I probably need about fifty of those because those are from the projects I am working on. Jenkins has all kinds of options and plugins to make sense of it all. In this chapter, we...
