> On Apr 25, 2018, at 12:04 AM, Chris Lambertus <c...@apache.org> wrote:
>
> The artifacts do not need to be kept in perpetuity. When every project does
> this, there are significant costs in both disk space and performance. Our
> policy has been 30 days or 10 jobs retention.
That policy wasn’t always in place.
> Please dispense with the passive aggressive “unwilling to provide” nonsense.
> This is inflammatory and anti-Infra for no valid reason. This process is
> meant to be a pragmatic approach to cleaning up and improving a service used
> by a large number of projects. The fact that I didn’t have time to post the
> job list in the 4 hours since my last reply does not need to be construed as
> reticence on Infra’s part to provide it.
I apologize. I took Greg’s reply as Infra’s official “Go Pound Sand”
response to what I felt was a reasonable request for more information.
> Using the yetus jobs as a reference, yetus-java builds 480 and 481 are nearly
> a year old, but only contain a few kilobytes of data. While removing them
> saves no space, they also provide no value,
… to infra.
The value to the communities that any job services is really up to
those communities to decide.
Thank you for providing the data. Now the projects can determine what
they need to save and perhaps change process/procedures before infra wipes it
out.
