Hi all, I think we can all agree on a 4 week (30 days) period for archiving the binaries?
Looking at: https://nightlies.apache.org/openoffice/install/linux64/?C=M;O=D we should also think about shortening the filenames. For example the Git hash could be reduced to the first 10 digits. Opinions? Regards, Matthias Am 22.01.23 um 09:31 schrieb Peter kovacs: > The output from git --log can be filtered to a since date. If we use the last > build date then we can check if there are entries. > Maybe some other switches would help. > > Am 21. Januar 2023 15:03:02 MEZ schrieb Matthias Seidel > <matthias.sei...@hamburg.de>: >> Hi Gavin, >> >> Am 21.01.23 um 13:33 schrieb Gavin McDonald: >>> Hi All, >>> >>> The nightly builds at https://ci2.apache.org/#/builders/58 are using up >>> much unnecessary >>> disk space on the nightlies.apache.org server. >>> >>> Currently Openoffice alone is using more than 1TB - all due to these >>> nightly builds. >>> Over 600GB are the linux64 snapshots and the rest are the linsnap* ones. >>> >>> Many many of these snapshots are identical to previous ones, but because >>> the date of the build is included then they are just repeated each day. >>> Even if no commits for weeks there is multi GB tars and debs being uploaded >>> each day. >>> >>> This seems a waste. >>> >>> Not only this, but no snapshots are being cleaned up, we have snapshots >>> dating back nearly a year just sitting there. >>> >>> Lets clean this up and be smarter going forwards. >>> >>> I would like to see these nightlies changed :- >>> >>> 1. Change to run weekly instead of daily. >>> 2. Instead of, or in addition to 1, build and upload by commit trigger. >> Just to clarify: >> >> I think the logic should be: Look every day (night) if there was a code >> change. If yes, do a build, otherwise skip. >> >> I don't want to trigger a build with every single commit... ;-) >> >> Regards, >> >> Matthias >> >>> 3. Clean up snapshots older than 1 month. >>> >>> Thoughts please >>>
smime.p7s
Description: S/MIME Cryptographic Signature
