From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Subject: | Re: Cirrus-ci is lowering free CI cycles - what to do with cfbot, etc? |
Date: | 2023-08-08 14:28:49 |
Message-ID: | db1d146f-42b4-b28c-0d70-a53182e9bef2@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08.08.23 04:15, Andres Freund wrote:
> Potential paths forward for individual CI:
>
> - migrate wholesale to another CI provider
>
> - split CI tasks across different CI providers, rely on github et al
> displaying the CI status for different platforms
>
> - give up
With the proposed optimizations, it seems you can still do a fair amount
of work under the free plan.
> Potential paths forward for cfbot, in addition to the above:
>
> - Pay for compute / ask the various cloud providers to grant us compute
> credits. At least some of the cloud providers can be used via cirrus-ci.
>
> - Host (some) CI runners ourselves. Particularly with macos and windows, that
> could provide significant savings.
>
> - Build our own system, using buildbot, jenkins or whatnot.
I think we should use the "compute credits" plan from Cirrus CI. It
should be possible to estimate the costs for that. Money is available,
I think.
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2023-08-08 14:28:53 | Re: Use of additional index columns in rows filtering |
Previous Message | Robert Haas | 2023-08-08 14:16:07 | Re: initial pruning in parallel append |