git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Junio C Hamano <gitster@pobox.com>,
	Roberto Tyley <roberto.tyley@gmail.com>
Cc: Jeff King <peff@peff.net>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Luke Diamand <luke@diamand.org>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Lars Schneider <larsxschneider@gmail.com>,
	Git Users <git@vger.kernel.org>
Subject: Re: [RFC/PATCH v1] Add Travis CI support
Date: Sun, 04 Oct 2015 10:13:49 +0200	[thread overview]
Message-ID: <1443946429.3520.3.camel@kaarsemaker.net> (raw)
In-Reply-To: <xmqq612n2z3d.fsf@gitster.mtv.corp.google.com>

On za, 2015-10-03 at 18:37 -0700, Junio C Hamano wrote:
> If somebody says "I've been maintaining a clone of git/git with
> Travis webhooks enabled and as the result caught this many glitches
> during the past two months without any ill side effect.

I've been maintaining a clone of git/git with a different ci system
enabled, and it hasn't really caught anything. Only the occasional test
failure in pu like the one I mailed about yesterday.

The automated testing of pull requests could be useful, but pull
requests don't seem to be used much yet.
-- 
Dennis Kaarsemaker
www.kaarsemaker.net

  reply	other threads:[~2015-10-04  8:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 21:43 [RFC/PATCH v1] Add Travis CI support larsxschneider
2015-09-24 21:43 ` larsxschneider
2015-09-25  0:41 ` Junio C Hamano
2015-09-25  3:14   ` Dennis Kaarsemaker
2015-09-25  7:27     ` Johannes Schindelin
2015-09-25  8:05       ` Luke Diamand
2015-09-25 17:41         ` Junio C Hamano
2015-09-26 16:40         ` Lars Schneider
2015-09-27 12:11         ` Matthieu Moy
2015-09-28 17:21           ` Stefan Beller
2015-09-28 17:37           ` Matthieu Moy
2015-09-28 18:47             ` Junio C Hamano
2015-09-28 19:07               ` Matthieu Moy
2015-10-03 22:23               ` Roberto Tyley
2015-10-04  1:27                 ` Junio C Hamano
2015-10-04  1:37                   ` Junio C Hamano
2015-10-04  8:13                     ` Dennis Kaarsemaker [this message]
2015-10-04 12:51                     ` Johannes Schindelin
2015-10-04  7:59                   ` Matthieu Moy
2015-10-04 17:46                     ` Junio C Hamano
2015-10-04 18:06                       ` Dennis Kaarsemaker
2015-10-05  6:54                         ` Matthieu Moy
2015-10-05 16:51                         ` Junio C Hamano
2015-10-12  8:03                       ` Sebastian Schuberth
2015-10-04 17:59                     ` Junio C Hamano
2015-10-04  3:34                 ` Jeff King
2015-10-02 16:40     ` Sebastian Schuberth
2015-09-25 16:26   ` Jeff King
2015-09-25 18:29     ` Junio C Hamano
2015-09-25 18:52       ` Jeff King
2015-09-26 21:54         ` Shawn Pearce

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=1443946429.3520.3.camel@kaarsemaker.net \
    --to=dennis@kaarsemaker.net \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=larsxschneider@gmail.com \
    --cc=luke@diamand.org \
    --cc=peff@peff.net \
    --cc=roberto.tyley@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;
as well as URLs for NNTP newsgroup(s).