Book Image

Learning Continuous Integration with Jenkins

By : Nikhil Pathania
Book Image

Learning Continuous Integration with Jenkins

By: Nikhil Pathania

Overview of this book

In past few years, Agile software development has seen tremendous growth across the world. There is huge demand for software delivery solutions that are fast yet flexible to frequent amendments. As a result, CI and continuous delivery methodologies are gaining popularity. Jenkins’ core functionality and flexibility allows it to fit in a variety of environments and can help streamline the development process for all stakeholders. This book starts off by explaining the concepts of CI and its significance in the Agile world with a whole chapter dedicated to it. Next, you’ll learn to configure and set up Jenkins. You’ll gain a foothold in implementing CI and continuous delivery methods. We dive into the various features offered by Jenkins one by one exploiting them for CI. After that, you’ll find out how to use the built-in pipeline feature of Jenkins. You’ll see how to integrate Jenkins with code analysis tools and test automation tools in order to achieve continuous delivery. Next, you’ll be introduced to continuous deployment and learn to achieve it using Jenkins. Through this book’s wealth of best practices and real-world tips, you'll discover how easy it is to implement a CI service with Jenkins.
Table of Contents (15 chapters)
Learning Continuous Integration with Jenkins
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

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