Q: Should we enable AppVeyor (Windows CI) for all repos?

[wilzbach]

What do you think about adding a Windows CI to our common standards (#7) for all repositories?
I personally haven't used Windows for years, but I do realize that it's a very important target and usually a bit neglected in the D community.

However, it's quite easy to add such a config and I made an Proof-of-Concept (PoC) one to libdparse: dlang-community/libdparse#141

If this allows to keep the build.bat in sync with the other builds i'm in favor. Make or build.bat or dub.json being broken is a recurrent issue. Also good because of the 32 bit build. In the past there's occasionally been size_t vs ulong errors.

[wilzbach]

Status tracker

Done

• Test Windows builds with AppVeyor libdparse#141
• Enable testing on Windows with AppVeyor DCD#383
• Enable testing on Windows with AppVeyor tinyendian#6
• Enable testing on Windows with AppVeyor D-YAML#65
• Enable testing on Windows harbored-mod#82
• Enable testing on Windows with AppVeyor dfmt#282
• Enable testing on Windows with AppVeyor dfix#44

Fail

• Enable testing on Windows with AppVeyor D-Scanner#437
• Enable testing on Windows with AppVeyor dsymbol#23

I've merged too fast yesterday. Actuallt it seems that all the bigger projects have issues: for example look at this:

• https://ci.appveyor.com/project/greenify/dcd/build/1.0.10/job/73e02kcrd9ol7m14#L81

I'm sorry but AppVeyor doesn't seem reliable enough. There are some random failures. They will annoy everybody when serious pull requests will come so i think we should revert what's been already merged.

[wilzbach]

I've merged too fast yesterday. Actuallt it seems that all the bigger projects have issues: for example look at this:

Hmm this seems to be an issue with Dub on Windows not AppVeyor ...

I'm sorry but AppVeyor doesn't seem reliable enough. There are some random failures. They will annoy everybody when serious pull requests will come so i think we should revert what's been already merged.

Can we simply disable the webhook? If Dub/Dub-registry issues gets fixed, we don't have to adjust the scripts anyway (or maybe only bump the version).
I already disabled the hooks for DCD & Dscanner:
https://github.com/dlang-community/DCD/settings/hooks/14284880

Is there another project where you observe this random dependency errors?

Btw we might, of course, try to use git submodules and avoid using DUB entirely, which would be a workaound against the DUB problems ...

Yes disable the hook for those that fail. Red crosses when the PR is clean are not acceptable. There were just those two so this OK for now.