Hi, On 2023-04-11 19:44:20 +0200, Alvaro Herrera wrote: > On 2023-Apr-11, Michael Paquier wrote: > > > Getting a CI job able to do some validation for MSVC would be indeed > > nice. What's the plan in the buildfarm with this coverage? Would all > > the animals switch to meson (Chocolatey + StrawberryPerl, I assume) > > for the job or will there still be some coverage with MSVC for v16 > > there? > > If we keep MSVC support in 16, then I agree we should have a CI task for > it -- and IMO we should make ti automatically triggers whenever any > Makefile or meson.build is modified. Hopefully we won't touch them > much now that the branch is feature-frozen, but it could still happen.
Once 16 branched, we can just have it always run, I think. It's just the development branch where it's worth avoiding that (for cfbot and personal hackery). I guess we could do something like: manual: "changesInclude('**.meson.build', '**Makefile*', '**.mk', 'src/tools/msvc/**')" so the task would be manual triggered if none of those files change. If you have write rights on the repository in question, you can trigger manual tasks with a click. > Do we have code for it already, even if incomplete? My meson branch has a commit adding a bunch of additional tasks. Including building with src/tools/msvc, building with meson + msbuild, openbsd, netbsd. https://github.com/postgres/postgres/commit/8f7c2ffb5a5e8f0ef3722e2439484187c1356416 Currently src/tools/msvc does build successfully, although the tests haven't finished yet: https://cirrus-ci.com/build/6298699714789376 (the cause for the opensuse failure is known, need to find cycles to tackle that, not related to meson) Greetings, Andres Freund