Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Continuous Integration with Jenkins

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

Arrow left icon
Product type Paperback
Published in Jan 2024
Publisher Packt
ISBN-13 9781835087732
Length 396 pages
Edition 3rd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Nikhil Pathania Nikhil Pathania
Author Profile Icon Nikhil Pathania
Nikhil Pathania
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

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 18. Other Books You May Enjoy

Discarding old builds in Jenkins

As more and more projects start to do CI/CD, Jenkins accumulates a large number of builds, each with its logs, artifacts, and other associated data. If not managed properly, this can lead to excessive disk space usage, making the Jenkins server sluggish or even causing disk outages. Hence, discarding old builds becomes an essential housekeeping task.

In the following section, we’ll delve into methods for cleaning up older builds in Jenkins. But before we do, let’s touch on the key reasons behind the necessity of discarding outdated builds. The following are a few important reasons:

  • Disk space conservation: Jenkins stores build logs, artifacts, and other metadata for every build. Over time, these accumulate and consume a significant amount of disk space.
  • Performance: Large numbers of old builds can slow down the Jenkins UI, making it challenging to navigate and retrieve necessary information.
  • Relevance: As code evolves...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image