From: Lars Schneider <larsxschneider@gmail.com>
To: Daniel Stenberg <daniel@haxx.se>
Cc: Git Mailing List <git@vger.kernel.org>,
Johannes.Schindelin@gmx.de, Jeff King <peff@peff.net>,
Junio C Hamano <gitster@pobox.com>,
Samuel Lijin <sxlijin@gmail.com>,
Sebastian Schuberth <sschuberth@gmail.com>
Subject: Re: [PATCH v2] travis-ci: build and test Git on Windows
Date: Fri, 24 Mar 2017 13:35:51 +0100 [thread overview]
Message-ID: <CD7E9F8C-77CA-44D4-AEC8-CEACD0528E3A@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1703241242210.17768@tvnag.unkk.fr>
> On 24 Mar 2017, at 12:48, Daniel Stenberg <daniel@haxx.se> 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
next prev parent reply other threads:[~2017-03-24 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 11:37 [PATCH v2] travis-ci: build and test Git on Windows Lars Schneider
2017-03-24 11:48 ` Daniel Stenberg
2017-03-24 12:35 ` Lars Schneider [this message]
2017-03-24 12:42 ` Daniel Stenberg
2017-03-24 12:43 ` Sebastian Schuberth
2017-03-29 23:26 ` Johannes Schindelin
2017-03-24 14:59 ` Jeff King
2017-03-24 16:58 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CD7E9F8C-77CA-44D4-AEC8-CEACD0528E3A@gmail.com \
--to=larsxschneider@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=daniel@haxx.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sschuberth@gmail.com \
--cc=sxlijin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox