Re: ci: Allow running mingw tests by default via environment variable
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Nathan Bossart <nathandbossart@gmail.com>,
Thomas Munro <thomas.munro@gmail.com>
Cc: Nazir Bilal Yavuz <byavuz81@gmail.com>, pgsql-hackers@postgresql.org,
Wolfgang Walther <walther@technowledgy.de>,
Heikki Linnakangas <hlinnaka@iki.fi>, Tomas Vondra <tomas@vondra.me>
Date: 2025-04-14T19:26:59Z
Lists: pgsql-hackers
Hi, On April 14, 2025 9:22:40 PM GMT+02:00, Nathan Bossart <nathandbossart@gmail.com> wrote: >On Sat, Apr 12, 2025 at 08:18:35PM +1200, Thomas Munro wrote: >> Is it safe to assume that CI changes come under the same code-freeze >> exception as tests and docs? I would assume so, it's just scripting >> glue in .cirrus.XXX files not affecting one bit of the software, but I >> don't recall that we specifically clarified that before, so can >> someone from the RMT please +1 this? Then I'll go ahead and push >> these. > >That seems reasonable to me. But to play devil's advocate, is there a >strong reason for doing this before July? We get more coverage of the changes we merge until then. Greetings, Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Commits
-
ci: Simplify ci-os-only handling
- b3aa95b61e90 15.15 landed
- 97d6ee571325 18.0 landed
- 60b64e6a31a2 19 (unreleased) landed
- 4900179e9cd8 16.11 landed
- 73f107b54ec6 17.7 landed
-
ci: Per-repo configuration for manually trigger tasks
- 49cba82bec1f 19 (unreleased) landed
- 88f3f7fd831e 15.15 landed
- 965d0a0b8b40 16.11 landed
- 3d478f66b651 17.7 landed
- faa78bc1c1d4 18.0 landed