Page MenuHomeSoftware Heritage

Do not keep more than 6 months of build history for python builds
ClosedPublic

Authored by vsellier on Apr 5 2022, 6:36 PM.

Details

Summary

It will free a lot of space on the build server

Diff Detail

Repository
rCJSWH Jenkins jobs
Branch
master
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 28228
Build 44195: arc lint + arc unit

Event Timeline

vsellier retitled this revision from Do not keep more the 6 months of build history for python builds to Do not keep more than 6 months of build history for python builds.Apr 5 2022, 6:40 PM
anlambert added a subscriber: anlambert.

Fine with me too.

This revision is now accepted and ready to land.Apr 6 2022, 10:41 AM

I don't like the idea of removing all old build logs indiscriminately, but it seems that noone else cares enough to do a more targeted analysis of what should be removed or not, so *shrug*.

The build discarder should be enabled on docs diffs builds too, each one generates 100MB of output.

(specific targets if we're looking at less indiscriminate removals: docs diffs html output, coverage reports, ccm reports, mochawesome reports, duplicated junit-formatted test reports)

Thanks olasd for the feedback.

I have updated the diff to reduce the build history of the biggest doc workspace build-on-diff to 90 days.
There is only ~150 today so keeping 180 days won't change anything.

I tried to be more selective as you proposed but I'm not sure if it's possible. It seems the
html reports are not managed as build artifacts but as an output of the html publisher plugin.
The only way I've found is to change the keep-all[1] property to false but in this case, only one
report will be kept, which is even worse.

Do you have another idea to achieve that in mind?

[1] https://forge.softwareheritage.org/source/swh-jenkins-jobs/browse/master/jobs/templates/swh-docs-pipeline-diff.groovy.j2$88

I tried to be more selective as you proposed but I'm not sure if it's possible. It seems the
html reports are not managed as build artifacts but as an output of the html publisher plugin.
The only way I've found is to change the keep-all[1] property to false but in this case, only one
report will be kept, which is even worse.

Yeah, that's unfortunate.

Do you have another idea to achieve that in mind?

Not really, unfortunately.

I think you can lower all days-to-keep to 90. Worst case, if some diff has been lingering for that long, we'll have to run the tests again anyway.

reduce the history to 90 days

This revision was automatically updated to reflect the committed changes.