Hi Rory,

Am 21.01.23 um 14:18 schrieb Rory O'Farrell:
> On Sat, 21 Jan 2023 14:13:54 +0100
> Matthias Seidel <matthias.sei...@hamburg.de> wrote:
>
>> Hi Rory,
>>
>> Am 21.01.23 um 13:52 schrieb Rory O'Farrell:
>>> On Sat, 21 Jan 2023 13:33:38 +0100
>>> Gavin McDonald <gmcdon...@apache.org> wrote:
>>>
>>>> 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.
>>>> 3. Clean up snapshots older than 1 month.
>>>>
>>>> Thoughts please
>>>>
>>> Agreed - the nightlies run well, as far as my use of them uses their 
>>> features.  A weekly build would be good, and no need to have extended 
>>> availability of older builds further back than (say) four weeks - four/five 
>>> weeks might be simpler to program than a month.
>> A nightly build of trunk should run every day *if* there was a code
>> change. This is important for developers to see if something they
>> committed does break the build process.
> I had (silently) assumed this would happen. I thought it a detail in the 
> overall picture of removing and re-ordering the nightlies.

No, Gavin wrote, that it doesn't happen...

And a nightly is a nightly. Otherwise it would be a weekly? ;-)

Regards,

   Matthias

>
> Rory  
>
>
>> The other branches (AOO42X, AOO41X) only build a snapshot once a week.
>>
>> Four weeks are a good period to have archived if a regression occurs.
>>
>> @Gavin: We discussed at some point, if we can trigger nightlies only if
>> there was a commit (change in git hash) but we didn't know how to do it.
>> So I would prefer 2. instead of 1. and concur with 3.
>>
>> Regards,
>>
>>    Matthias
>>
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to