retention history changed, closing

I've sent https://gerrit.ovirt.org/#/c/78707/ to increase the build history for now.

The retention policy is defined in the templates (under jobs/conf/yaml/templates), look for

"{project}_{version}_build-artifacts-{distro}-{arch}{_big_artifacts}"

I don't see any retention settings in the job configuration yaml and not entirely sure where they're inherited from.

As for build #97 - it is marked with the "keep this build forever" tag, that's why it was not deleted.

There were more than 2 builds in the job's history after Sep 2016... why did it save that single job from 2016 ?

Can you check what is the current configuration in YAML for keeping history for this job?

This job has "Max # of builds to keep" equal to 2 so all older builds are deleted by Jenkins itself. I do not see any "max-total: 2" configuration in our YAMLs so not sure when this change was introduced. Recent job config history doesn't have anything related to changes in this parameter:
http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/jobConfigHistory/

Yes, is right, I think the deletion messed up lastSuccessful, making it point to some old version. However, using the rpm would mean a bigger change, and it would take a little more time to run (extract the rpm etc). I think that the best way to fix this, is to copy the squashfs from its original place to the exported-artifacts dir with a timestamp, so instead of cp <squashfs> exported-artifacts, it would be something like cp squashfs exported-artifacts/squashfs-<builddate>, and let image-ng continue to pick up the squashfs by a build number.