All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: "Jason Pyeron" <jpyeron@pdinc.us>,
	git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Ramsay Jones" <ramsay@ramsayjones.plus.com>
Subject: Re: Continous Integration (was: RE: Git v2.13.1 SHA1 very broken)
Date: Sun, 2 Jul 2017 21:35:48 +0100	[thread overview]
Message-ID: <20170702203548.GA26574@dinwoodie.org> (raw)
In-Reply-To: <CF387D0C-6743-4B88-A4CC-D6310A634E03@gmail.com>

On Tue, Jun 06, 2017 at 05:04:32PM +0200, Lars Schneider wrote:
> > On 06 Jun 2017, at 16:47, Jason Pyeron <jpyeron@pdinc.us> wrote:
> > 
> > Do we have Jenkins (or something else) setup for Git?
> > 
> > We would be happy to donate (slave) VMs for cygwin builds og Git.  
> > 
> > -Jason Pyeron
> > 
> 
> We use TravisCI for Linux, Mac, and (in a special way) Windows: 
> https://travis-ci.org/git/git
> 
> Windows is not supported by TravisCI. We just use TravisCI to
> trigger a build on MS Azure and read the results:
> https://github.com/git/git/commit/029aeeed55f6bfe8014e8ffe5fc7a6f2e5b110fc
> 
> Maybe we could trigger a Cgywin build on your slaves in the same way?

I tried setting up a Cygwin Git build on AppVeyor a little while ago,
but the problem I found is that Cygwin builds are slow, particularly if
you want to also run the test suite.  I do the builds for the Cygwin
distribution on my normal PC (so reasonably powerful but definitely not
devoted to the purpose), and doing the build and running the default
tests takes in the region of 8 hours for the 64-bit build and 12 hours
for the 32-bit build.

At the moment, I'm trying to set up automated regular builds on my PC
using BuildBot.  I think that, short of someone donating some fairly
significant resources for Cygwin builds, that's going to be the closest
I'll be able to find for spotting problems early.  It's a project in my
currently limited spare time, though, and not something I've done
before, so it's taking a little while to get going.

Adam

  reply	other threads:[~2017-07-02 20:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 20:34 Git v2.13.1 SHA1 very broken Adam Dinwoodie
2017-06-05 21:05 ` Ævar Arnfjörð Bjarmason
2017-06-05 23:20   ` Ramsay Jones
2017-06-06  0:11     ` Ramsay Jones
2017-06-06  1:20   ` Junio C Hamano
2017-06-06 10:03     ` Adam Dinwoodie
2017-06-06 11:55       ` Junio C Hamano
2017-06-06 12:43         ` Adam Dinwoodie
2017-06-06 14:47           ` Continous Integration (was: RE: Git v2.13.1 SHA1 very broken) Jason Pyeron
2017-06-06 15:04             ` Lars Schneider
2017-07-02 20:35               ` Adam Dinwoodie [this message]
2017-07-03 12:34                 ` Johannes Schindelin
2017-06-06 15:12           ` [PATCH 0/3] update sha1dc Ævar Arnfjörð Bjarmason
2017-06-06 15:12             ` [PATCH 1/3] sha1dc: update from upstream Ævar Arnfjörð Bjarmason
2017-06-06 15:12             ` [PATCH 2/3] sha1dc: optionally use sha1collisiondetection as a submodule Ævar Arnfjörð Bjarmason
2017-06-06 18:48               ` Stefan Beller
2017-06-06 19:03                 ` Ævar Arnfjörð Bjarmason
2017-06-06 19:09                   ` Stefan Beller
2017-06-06 15:12             ` [PATCH 3/3] sha1collisiondetection: automatically enable when submodule is populated Ævar Arnfjörð Bjarmason
2017-06-06 18:23             ` [PATCH 0/3] update sha1dc Stefan Beller
2017-06-06 18:51               ` Ævar Arnfjörð Bjarmason
2017-06-06 19:01                 ` [PATCH] sha1dc: ignore indent-with-non-tab whitespace violations Jeff King
2017-06-06 19:04                   ` Ævar Arnfjörð Bjarmason
2017-06-06 19:05                   ` Stefan Beller
2017-06-13  2:09             ` [PATCH 0/3] update sha1dc Liam R. Howlett
2017-06-06 12:49         ` Git v2.13.1 SHA1 very broken Morten Welinder

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=20170702203548.GA26574@dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jpyeron@pdinc.us \
    --cc=larsxschneider@gmail.com \
    --cc=ramsay@ramsayjones.plus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.