Summary
In this chapter, we saw how to implement Continuous Delivery using Jenkins along with testing tools such as JMeter, TestNG, and Selenium. We also saw how to create parameterized Jenkins jobs and configure Jenkins slave agents.
The parameter plugin that comes by default in Jenkins helped our Jenkins jobs pass important information among themselves, such as the version of code to build and version of artifact to deploy.
To keep things simple, we chose to perform all the testing on a single testing server, where we also configured our Jenkins slave agent. However, this is not something that you will see in most organizations. There can be many Jenkins nodes running on many testing servers, with each testing server dedicated to performing a specific test.
Feel free to experiment yourself by configuring a separate machine for user acceptance testing and performance testing. Install the Jenkins node agent on both the machines and modify your Jenkins jobs that perform user acceptance tests...
