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

Creating a nice visual flow for the Continuous Integration pipeline


So far, we have created around six Jenkins jobs in total, segregated across three Jenkins pipelines:

  • Pipeline to poll the Feature1 branch:

    • Poll_Build_UnitTest_Feature1_Branch

    • Merge_Feature1_Into_Integration_Branch

  • Pipeline to poll the Feature2 branch:

    • Poll_Build_UnitTest_Feature2_Branch

    • Merge_Feature2_Into_Integration_Branch

  • Pipeline to poll the integration branch:

    • Poll_Build_StaticCodeAnalysis_IntegrationTest_Integration_Branch

    • Upload_Package_To_Artifactory

All the three pipelines combined complete our CI Design.

Note

There were actually two Jenkins pipelines discussed as part of our CI Design. However, we have three now. This is just because we have two feature branches; we still have two types of Jenkins pipeline.

In this section, we will create a view inside the Jenkins Dashboard using the delivery pipeline plugin. This view is a nice way of presenting the CI flow. The same plugin will also be used to create a Continuous...