> On Apr 26, 2022, at 10:47 AM, Zowalla, Richard > <[email protected]> wrote: > > However, we need to carefully monitor the disk usage / volume used as > INFRA has a problem if our used storage volume per jobs exceeds a > certain quota. > > We occupied 1,5T last week (cumulated over a few weeks) and they were a > bit mad as the Jenkins CI env went out of storage.
I was going to jump in on that thread and got side tracked. I wonder if we can do a `mvn clean` or something similar as a post build step. Looks like after a build we have 2.8G used of disk space and once we clean that goes down to 398M. The test case results are the obvious trick. I'm not sure if Jenkins keeps those somewhere else or if we need them to keep living in the target directories. If they need to stay in the target directories we can maybe create a script that deletes everything in target/ but surefire results. If we did that, we'd use 1.5 gigabytes for 30 builds vs 10.5 gigabytes. Then we could just keep 30 builds regardless of days and it should be good. Thoughts? -David
smime.p7s
Description: S/MIME cryptographic signature
