git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Luke Diamand <luke@diamand.org>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Dennis Kaarsemaker <dennis@kaarsemaker.net>,
	Junio C Hamano <gitster@pobox.com>,
	Lars Schneider <larsxschneider@gmail.com>,
	Git Users <git@vger.kernel.org>
Subject: Re: [RFC/PATCH v1] Add Travis CI support
Date: Mon, 28 Sep 2015 10:21:51 -0700	[thread overview]
Message-ID: <CAGZ79karJa0KfMcqwXopZ5Uuh1ocDizH=fFqFDS+Jw-kTc-wng@mail.gmail.com> (raw)
In-Reply-To: <vpq7fnc83ki.fsf@grenoble-inp.fr>

On Sun, Sep 27, 2015 at 5:11 AM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
>
> My experience with Travis-CI is that it just works

I can second that.
When I was contributing to other projects[1][2], Travis helped a lot.

Currently I have a cronjob to get https://scan.coverity.com/
running on Git a few times a week on the pu branch
(plus $gmane/271826). Additionally to that I could setup
a travis test to that, which would run daily on stefanbeller/pu
(which would be a copy of junios pu branch).

I just logged in to travis and it seems as if they don't require
write access to the repository (any more? They used to require
it, but now they ask for updated permissions which drops
write access to a repository, but then asks for more meta
data permissions, such as web hooks, my email address,
my organizations).

Having observed that there is no reason to not turn it on on
the main repository (set it and forget it).

[1] https://github.com/bjorn/tiled
[2] https://github.com/clintbellanger/flare-engine



>
>   http://docs.travis-ci.com/user/notifications/
>
>   "By default, email notifications are sent to the committer and the
>   commit author, if they are members of the repository (that is, they
>   have push or admin permissions for public repositories, or if they
>   have pull, push or admin permissions for private repositories)."
>
> In short:
>
> * If the tests always pass, nobody ever get any email from Travis-CI.
>
> * When someone sends a pull-request that fails tests, that someone gets
>   an automatic email about the failure. This saves one email round-trip
>   "X sends a patch series, Junio notices the failure, Junio sends an
>   email about the failure", and shortcuts this as "X sends a PR, and
>   gets an email, possibly even before Junio notices".
>
>> Automated testing is a Good Thing, but it's still software, so needs
>> maintenance or it will break.
>
> The point of using Travis-CI is precisely to use an externally
> maintained system. It's not just software, it's a service (based on
> software, obviously).
>
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-09-28 17:21 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 [this message]
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
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='CAGZ79karJa0KfMcqwXopZ5Uuh1ocDizH=fFqFDS+Jw-kTc-wng@mail.gmail.com' \
    --to=sbeller@google.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=dennis@kaarsemaker.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=larsxschneider@gmail.com \
    --cc=luke@diamand.org \
    /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).