| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | how to manage Cirrus on personal repository |
| Date: | 2023-09-29 09:13:24 |
| Message-ID: | 3fd11fe8-38df-f2aa-1b00-f91362c8c382@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I have a private repository on GitHub where I park PostgreSQL
development work. I also have Cirrus activated on that repository, to
build those branches, using the existing Cirrus configuration.
Now under the new system of limited credits that started in September,
this blew through the credits about half-way through the month.
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?
I suppose one way to deal with this is to make a second repository and
only activate Cirrus on that one, and push there on demand.
Any ideas?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-09-29 09:26:55 | Re: Remove MSVC scripts from the tree |
| Previous Message | Peter Eisentraut | 2023-09-29 09:05:15 | Re: pg_resetwal regression: could not upgrade after 1d863c2504 |