Darin, this rocked so hard. I knew there was a way to trigger the agent that discards builds and then you treated me to a way to control retention across all my jobs. Yess!
Darin, many thanks! Funny that youtube offered me this video today. Yesterday I had to dig deep in to the history of a job and wondered how if any there was a build clean-up, now I known where to look for!
Perfect! Thanks!!! Quick Question: Where is the documentation that shows how to run the GlobalBuildDiscarder right away? You mention its in the "pull request" for this feature, but I can't find it.
What if your authors aren't well behaved and mark everything "Keep Forever" (or use the option you've shown)... We need to know how to stop THAT bad behavior too (e.g. find all builds marked keep forever and unset that value). "Don't let them mark all of them as keep" - How do you do that - you've just pointed out it's very easy to automate. IMHO the number of retained builds should be enforced INCLUDING the keep forever. E.g. if I have "keep 10 builds" as my maximum, and I mark 11 as kept, the first thing that should happen is that the 11th kept build should be discarded. The next thing that should happen is that each subsequent build should discard the oldest keep forever build.
![เปิดบ้าน โคตรสวย ป๋องกพล รู้จักตั้งนาน เพิ่งรู้ว่ารวย!!! l [Nickynachat]](http://i.ytimg.com/vi/tmgCF_2HfYI/mqdefault.jpg)
Darin, this rocked so hard. I knew there was a way to trigger the agent that discards builds and then you treated me to a way to control retention across all my jobs. Yess!
Darin, many thanks! Funny that youtube offered me this video today. Yesterday I had to dig deep in to the history of a job and wondered how if any there was a build clean-up, now I known where to look for!
Perfect! Thanks!!!
Quick Question: Where is the documentation that shows how to run the GlobalBuildDiscarder right away? You mention its in the "pull request" for this feature, but I can't find it.
You are awesome !!
Thank you so much!
That was really great ... and what if if you want them back for some reason ...can we revert it . or can we bring back old builds for jobs ?
veru good tpic and video, thank for helping me
Hi Darin,
Does this work for Multibranch pipelines at all ?
对我很有帮助，感谢！
Hi, this vedio was very good,thank you for helping. i have a question, how to fix low space in jenkins? if i can't access on it during SSH?
What If I do not want those builds that have been tagged as "Release:-" builds not to be removed?
How does one cleanup the code checked out on the "built-in" node in order to execute on a Jenkinsfile?
How to force clean the keep builds？I feel the keep build is a loop hole and people is going to abuse it
What if your authors aren't well behaved and mark everything "Keep Forever" (or use the option you've shown)... We need to know how to stop THAT bad behavior too (e.g. find all builds marked keep forever and unset that value).
"Don't let them mark all of them as keep" - How do you do that - you've just pointed out it's very easy to automate. IMHO the number of retained builds should be enforced INCLUDING the keep forever. E.g. if I have "keep 10 builds" as my maximum, and I mark 11 as kept, the first thing that should happen is that the 11th kept build should be discarded. The next thing that should happen is that each subsequent build should discard the oldest keep forever build.