Hi, On Fri, 24 Mar 2017, Sebastian Schuberth wrote:
> On Fri, Mar 24, 2017 at 1:35 PM, Lars Schneider > <larsxschnei...@gmail.com> wrote: > > >> 1. use appveyor.com, as that is a Travis-like service for Windows. We do > >> our > >> windows-builds in the curl project using that. > > > > The Git for Windows build and tests are *really* resources intensive and > > they > > take a lot of setup time. AFAIK we would run into timeouts with AppVeyor. > > Maybe Sebastian or Dscho know details? > > At lot of setup time, in terms of installing the Git for Windows SDK, > could probably be saved by only installing the required packages on > top of MSYS2 that's already installed in AppVeyor nodes [1]. > > [1] https://www.appveyor.com/docs/build-environment/#mingw-msys-cygwin And that is indeed what Git for Windows' Git fork has configured. Sadly, the job timed out too often for me, even if I disabled the tests. As of recent, things turned more green, with the build taking only about 3 minutes. Of course, re-enabling the tests would let us run smack into the 20 minutes time out, *and* we still would have to disable the tests that fail because MSYS2's maintainer ignored the PRs trying to integrate Git for Windows' patches to the MSYS2 runtime. Example for a green job: https://ci.appveyor.com/project/dscho/git/build/1.0.676 Ciao, Johannes
