| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Wolfgang Walther <walther(at)technowledgy(dot)de> |
| Subject: | Re: ci: Allow running mingw tests by default via environment variable |
| Date: | 2025-04-07 13:43:01 |
| Message-ID: | 57gn2n5c3s33qfshlbgy472l3bn3wlaj7mmv4zrlx7s262zm3o@b5n4ajezb5x7 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2025-04-07 16:03:48 +0300, Nazir Bilal Yavuz wrote:
> On Wed, 5 Mar 2025 at 18:51, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > I'm inclined to think we should apply to this to all branches with CI support,
> > not just master. It's kind of annoying to have CI infrastructure changes like
> > this that differ between branches. Thoughts?
>
> I am sharing patches per branch until we come up with a better
> solution. Some remarks:
>
> REL_15: It doesn't have any manual tasks, so per repository trigger
> patch (Thomas' patch) is omitted.
> REL_16: Only Mingw task is manual.
> REL_17: Only Mingw task is manual.
>
> While rebasing them, I realized that we use
> 'REPO_CI_AUTOMATIC_TRIGGER_TASKS' for all branches. So, we don't have
> per branch 'REPO_CI_AUTOMATIC_TRIGGER_TASKS' configuration option. Is
> that a problem?
I think that's not a problem. I can't think of a case where one would want to
do this only for some of the branches. Does anybody disagree?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2025-04-07 13:50:42 | Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate |
| Previous Message | Daniel Gustafsson | 2025-04-07 13:41:37 | Re: Enhancing Memory Context Statistics Reporting |