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

Maintaining your Jenkins setup

To ensure the longevity and stability of a Jenkins environment, ongoing maintenance is essential. Upgrading Jenkins involves careful planning and execution to leverage new features, security enhancements, and bug fixes effectively. Backup strategies and disaster recovery best practices safeguard critical Jenkins server data and ensure business continuity. Troubleshooting techniques and community support resources aid in addressing common issues and seeking timely assistance when needed.

Following a structured approach to upgrades

Upgrading Jenkins, or any other DevOps tool for that matter, is critical if you want to take advantage of new features, bug fixes, security updates, and performance improvements. IT security teams in any organization are well aware of this and they do so by frequently sending proactive emails to users and administrators informing them about the availability of a security patch related to the tools in use. These emails act...