Re: how to manage Cirrus on personal repository

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: how to manage Cirrus on personal repository
Date: 2023-09-29 10:38:48
Message-ID: AD7FF57F-BDFA-4BC0-97F1-60C9B6381132@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 29 Sep 2023, at 11:13, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:

> Does anyone have an idea how to manage this better? Is there maybe a way to globally set "only trigger manually", or could we make one?

On my personal repo I only build via doing pull-requests, such that I can
control when and what is built and rate-limit myself that way. Using the
Github CLI client it's quite easy to script "push-and-build". Not sure if it's
better, it's just what I got used to from doing personal CI on Github before we
had Cirrus support in the tree.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-09-29 10:59:19 Re: [PoC] pg_upgrade: allow to upgrade publisher node
Previous Message vignesh C 2023-09-29 10:19:54 Re: Testing autovacuum wraparound (including failsafe)