You're reading from Learning Continuous Integration with Jenkins An end-to-end guide to creating operational, secure, resilient, and cost-effective CI/CD processes

Product type Paperback

Published in Jan 2024

Publisher Packt

ISBN-13 9781835087732

Length 396 pages

Edition 3rd Edition

Tools

Jenkins

Concepts

Continuous Integration

Author (1):

Nikhil Pathania

View More author details

Table of Contents (19) Chapters

Preface

1. Part 1: The Concepts FREE CHAPTER

2. Chapter 1: The What, How, and Why of Continuous Integration

3. Part 2: Engineering the CI Ecosystem

4. Chapter 2: Planning, Deploying, and Maintaining Jenkins

5. Chapter 3: Securing Jenkins

6. Chapter 4: Extending Jenkins

7. Chapter 5: Scaling Jenkins

8. Part 3: Crafting the CI Pipeline

9. Chapter 6: Enhancing Jenkins Pipeline Vocabulary

10. Chapter 7: Crafting AI-Powered Pipeline Code

11. Chapter 8: Setting the Stage for Writing Your First CI Pipeline

12. Chapter 9: Writing Your First CI Pipeline

13. Part 4: Crafting the CD Pipeline

14. Chapter 10: Planning for Continuous Deployment

15. Chapter 11: Writing Your First CD Pipeline

16. Chapter 12: Enhancing Your CI/CD Pipelines

17. Index

Why subscribe?

18. Other Books You May Enjoy

Constructing a pipeline code using ChatGPT

Let us try a real experiment in the following section to harness the power of ChatGPT to build Continuous Integration (CI) pipeline code. We will prompt ChatGPT to produce basic pipeline code by giving a scenario and providing insights into the Jenkins environment. We will then iteratively refine the pipeline code as we enquire about individual stages and processes within the pipeline. This collaborative process yields a well-optimized CI pipeline that perfectly corresponds with project objectives and connects easily with platforms such as GitHub, SonarQube, and Artifactory. So let us get started.

The following is what we will ask ChatGPT based on the guidelines we learned earlier:

“Hi, I am working on a web application using the Java programming language and Maven to build, unit test, and package output as a .jar file. Can you create a CI pipeline that performs the following: