Chapter 1, Exploring Jenkins, describes in detail the basics of Continuous Integration and an overview of Jenkins. It describes the recent growth of importance of Continuous Integration as a practice to cultivate DevOps culture. This chapter also describes the installation and configuration of Jenkins. We are going to take a whistle-stop tour through some of the key features of Jenkins, and plugin installation as well.

Chapter 2, Installation and Configuration of Code Repositories and Build Tools, describes in detail how to prepare the runtime environment for application life cycle management and configure it with Jenkins - the open source continuous integration tool. It will cover how to integrate Eclipse and Jenkins, so builds can be run from Eclipse as well.

Chapter 3, Managing Code Quality and Notifications, will cover how to integrate static code analysis behavior into Jenkins. Code quality is an extremely vital feature that impacts on applications' effectiveness and by integrating it with Sonar, users get insights into problematic portions of code. This chapter also covers email notifications on build status.

Chapter 4, Continuous Integration with Jenkins, describes in detail how to create and configure build jobs in Java, how to run build jobs, unit test cases using Ant, and Maven build tools. It covers all aspects of running a build to create a distribution file or war file for deployment.

Chapter 5, Continuous Delivery - Implementing Automated Deployment, provides insights into how functional testing and load testing can be performed and how they can be integrated with Jenkins to adopt the Continuous Testing practices of DevOps culture.

Chapter 6, Continuous Testing - Functional and Load Testing with Jenkins, takes one step forward in the DevOps pipeline by deploying artifacts to local or remote application servers. It gives insights into automated deployment and Continuous Delivery processes, and also covers how to deploy applications to a public cloud platform using Jenkins.

Chapter 7, Build Pipeline and Pipeline as a Code, will cover how to orchestrate build job to execute them in a specific sequence. We will cover the Build Pipeline plugin and the Pipeline as a Code feature that is available in Jenkins 2 and later.

Chapter 8, Managing and Monitoring Jenkins, gives insight into the management of Jenkins nodes and monitoring them with Java Melody, in order to provide details on the utilization of resources. It also covers how to monitor build jobs configured for Java-or .NET-related applications, and managing those configurations by keeping backups of them.

Chapter 9, Security in Jenkins, will cover security management options available in Jenkins. This will help to perform user management, authentication, and authorization, including matrix-based security and role-based access.

This book is for beginners. This book assumes that you are familiar with at least the Java programming language. Knowledge of core Java and JEE is essential if you are to use this book to gain better insights. Having a strong understanding of programming logic will provide you with the background to be productive with Jenkins, while using plugins or writing commands for the shell.

As the application development life cycle will cover a lot of tools, it is essential to have some knowledge of repositories such as svn, git, and so on, IDE tools such as Eclipse, and build tools such as Ant and Maven.

Knowledge of code analysis tools will make jobs easier to configur and integrate, however, it is not required in order to complete the exercises presented in this book. Most of the configuration steps are mentioned clearly. SonarQuve version 6.3 is used for code analysis.

You will be walked through the steps required to install Jenkins on a Windows and Linux-based host. In order to be immediately successful, you will need administrative access to a host that runs a modern version of Windows and Linux; Windows 10 will be used for demonstration purposes. If you are a more experienced reader, then a recent release of almost any distribution will work just as well (but you may be required to do a little bit of extra work that is not outlined in the book).

Additionally, you will need access to the internet to download plugins that you do not already have, as well as an installation of Jenkins. Any normal hardware configuration is good enough, such as 4 GB RAM and 500 GB hard drive.

This book assumes that you are familiar with at least java programming language. Knowledge of core java and JEE is essential considering this book to gain better insight. Having a strong understanding of program logic will provide you with the background to be productive with Jenkins while using plugins of writing commands for shell.

As application development life cycle will cover lot of tools in general; it is essential to have some knowledge of repositories such as svn, git etc; IDE tools such as Eclipse; build tools such as ant and maven.

Knowledge of code analysis tools will make job easier in configuration and integration, however it is not extremely vital to perform exercises given in the book. Most of the configuration steps are mentioned clearly.

Additionally, you will need access to the Internet to download plugins that you do not already have, as well as an installation of the Jenkins.

In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows:

A block of code is set as follows:

#run the model
model <- OneR(train_data, frisked ~ ., verbose = TRUE)
#summarize the model
summary(model)
#run the sql function from the SparkR package
SparkR::sql("SELECT sample_bin , count(*)
\FROM out_tbl group by sample_bin")

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

#note we are specifing the SparkR filter, not the dplyr filer
head(SparkR::filter(out_sd1,out_sd1$sample_bin==1),1000)

Any command-line, (including commands at the R console) input or output is written as follows:

> summary(xchurn)

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "clicking the Next button moves you to the next screen."

Feedback from our readers is always welcome. Let us know what you think about this book-what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of. To send us general feedback, simply e-mail [email protected], and mention the book's title in the subject of your message. If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.