Re: [RFC/PATCH v1] Add Travis CI support

From: Stefan Beller <sbeller@google.com>
Date: Sep 28, 2015, 17:21 UTC
Message-ID: <CAGZ79karJa0KfMcqwXopZ5Uuh1ocDizH=fFqFDS+Jw-kTc-wng@mail.gmail.com>
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

Show 32 quoted lines

>
>   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