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

Why is continuous integration crucial?

The answer is straightforward: CI practices are critical because they enable teams to fulfill modern software development demands. But what are these demands, what benefits of CI help fulfill these demands, and how do they do so? This is what we'll look at in this section.

A faster time to market (TTM)

Also known as lead time or time to delivery, TTM is the time it takes a feature to get from its origin (typically a code change) to deployment in production. A higher TTM number indicates that features are being developed, tested, and delivered more slowly and infrequently. Most current software programs and services need more frequent software upgrades. So, let’s see some advantages of CI/CD that help achieve a lower TTM value: