Chapter 1, Concepts of Continuous Integration, has an account of how some of the most popular and widely used software development methodologies gave rise to Continuous Integration. It is followed by an in-depth explanation of the various requirements and best practices of Continuous Integration.

Chapter 2, Setting up Jenkins, is a step-by-step guide that is all about installing Jenkins across various platforms and particularly on the Apache Tomcat server.

Chapter 3, Configuring Jenkins, is an overview of how Jenkins looks and feels with an in-depth explanation of its important constituents. It is followed by a step-by-step guide to accomplishing some of the basic Jenkins administration tasks.

Chapter 4, Continuous Integration Using Jenkins – Part I, is a step-by-step guide that takes you through a Continuous Integration Design and the means to achieve it using Jenkins, in collaboration with some other DevOps tools.

Chapter 5, Continuous Integration Using Jenkins – Part II, is a continuation of the previous chapter.

Chapter 6, Continuous Delivery Using Jenkins, is a step-by-step guide that takes you through a Continuous Delivery Design and the means to achieve it using Jenkins, in collaboration with some other DevOps tools.

Chapter 7, Continuous Deployment Using Jenkins, explains the difference between Continuous Delivery and Continuous Deployment. It is followed by a step-by-step guide that takes you through a Continuous Deployment Design and the means to achieve it using Jenkins, in collaboration with some other DevOps tools.

Chapter 8, Jenkins Best Practices, is a step-by-step guide to accomplishing distributed builds using the Jenkins master-slave architecture. It is followed by some practical examples that depict some of the Jenkins best practices.

To set up the Jenkins server, you will need a machine with the following configurations.

Operating systems:

Software tools (minimum version):

Hardware requirements:

This book is aimed at readers with little or no previous experience with agile or Continuous Integration. It serves as a great starting point for everyone who is new to the field of DevOps and would like to leverage the benefits of Continuous Integration and Continuous Delivery in order to increase productivity and reduce delivery time.

Build and release engineers, deployment engineers, DevOps engineers, SCM (Software Configuration Management) engineers, developers, testers, and project managers all can benefit from this book.

The readers who are already using Jenkins for Continuous Integration can learn to take their project to the next level, which is Continuous Delivery. This book discusses Continuous Integration, Continuous Delivery, and Continuous Deployment using a Java-based project. Nevertheless, the concepts are still applicable if you are using other technology setups, such as Ruby on Rails or .NET. In addition to that, the Jenkins concepts, installation, best practices, and administration, remain the same irrespective of the technology stack you use.

In this book, you will find a number of text styles 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: "You have make and omake, and also clearmake if you are using IBM Rational ClearCase as the version control tool."

A block of code is set as follows:

# Print a message.
  print "Hello, World!\n";
  print "Good Morning!\n";

Any command-line input or output is written as follows:

cd /etc/sysconfig/
vi jenkins

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Click on the Install as Windows Service link."

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.