View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0013805||Buildsys||Ci.centos.org Ecosystem Testing||public||2017-09-14 07:57||2017-09-20 10:00|
|Summary||0013805: Remove old nightly Gluster builds from artifacts.c.c.o|
|Description||The Gluster Community builds packages for testing from the HEAD of the maintained branches in the upstream GlusterFS repository. It is useful to have some previous builds available, but we definitely do not need everything.|
All files that are located under http://artifacts.ci.centos.org/gluster/nightly/ can be deleted when they get older than 30 days.
|Tags||No tags attached.|
Do you need us to descend into the directory structure to look at the individual files, or can we delete the toplevel directories?
The way I understand it, if we were to run the process today we would remove the following directories, and everything under them:
- release-3.7/, AND
I'd be excluding the .repo files from pruning (since the active ones don't appear to be updated with the nightly builds)
Yes, you can remove those directories.
Also descent unto the other directories, as the .rpm files in them will become a few months old (and nobody uses them).
You may also delete the .repo files, not need to exclude them. https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/92 has been sent (waiting to be merged) so that the .repo files will be updated every night as well.