Hi Cesar, I have no problem with increasing the values for the discard strategy. It makes sense to keep it a bit longer for PRs.
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. Gruß Richard Am Dienstag, dem 26.04.2022 um 11:39 -0600 schrieb Cesar Hernandez: > Hello, > > Our current Discard old builds Strategy in CI for PR's for the master > branch is [1]: > Days to keep builds: 2 > Max # of builds to keep: 3 > > Is there any objection if I update this to at least: > Days to keep builds: 15 > Max # of builds to keep: 30 > > Currently, if one opens a PR on a Friday and tries to catch up on > mid-Monday next week, the PR results are gone. > The above proposal will also give us a bit more room for more context > on > how PR's and past builds have evolved, especially when trying to > chase and > resolve random test failures. > > > [1] > https://ci-builds.apache.org/job/Tomee/job/master-pull-request
smime.p7s
Description: S/MIME cryptographic signature
