how to manage Cirrus on personal repository - Mailing list pgsql-hackers

From Peter Eisentraut
Subject how to manage Cirrus on personal repository
Date
Msg-id 3fd11fe8-38df-f2aa-1b00-f91362c8c382@eisentraut.org
Whole thread Raw
Responses Re: how to manage Cirrus on personal repository
Re: how to manage Cirrus on personal repository
Re: how to manage Cirrus on personal repository
List 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?



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_resetwal regression: could not upgrade after 1d863c2504
Next
From: Peter Eisentraut
Date:
Subject: Re: Remove MSVC scripts from the tree