> On 24 Mar 2017, at 12:48, Daniel Stenberg <[email protected]> wrote: > > On Fri, 24 Mar 2017, Lars Schneider wrote: > >> Most Git developers work on Linux and they have no way to know if their >> changes would break the Git for Windows build. Let's fix that by adding a >> job to TravisCI that builds and tests Git on Windows. Unfortunately, >> TravisCI does not support Windows. > > Forgive me for bursting in and possibly repeating what you've already > discussed. I just read about the limitations for doing windows builds via > travis so I thought I'd at least let you know that you can avoid those > limitations without too much work:
You are not bursting in - I am happy to get your feedback! Thanks a lot for CURL BTW :-) > Two alternative approaches would be: > > 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? > 2. run your own buildbot and submit data using the regular github hook and > have buildbot submit the results back (it has a plugin that can do that). > We do solaris-builds in the curl project using that method (thanks to > opencsw.org) and some additional windows-builds thanks to private > individuals. We could do that! However, the idea was to have the entire build status for all platforms in one place. - Lars
