From: Lars Schneider <larsxschneider@gmail.com>
Date: Mon, 25 Apr 2016 08:35:24 GMT
Subject: Re: [PATCH v1] travis-ci: build documentation
Message-ID: <B674CC4C-5506-4E5C-B638-45E0FAD50842@gmail.com>
In-Reply-To: <20160423033922.GA15994@sigill.intra.peff.net>


On 23 Apr 2016, at 05:39, Jeff King <peff@peff.net> wrote:

> On Fri, Apr 22, 2016 at 10:34:02AM +0200, larsxschneider@gmail.com wrote:
> 
>> From: Lars Schneider <larsxschneider@gmail.com>
>> 
>> Run "make doc" to check if all documentation can be build without errors.
>> Since the documentation is the same on every platform/compiler, the check
>> is only performed as part of the Linux/GCC build job to maintain a fast
>> CI process.
> 
> This does slow down the normal test results for linux/gcc, though. I
> don't know very much about Travis, but is it possible to break out the
> documentation build into its own test, with a separate build status from
> the other runs?

Great idea. This is how it looks.

All jobs of a run:
https://travis-ci.org/larsxschneider/git/builds/125506781

The documentation job:
https://travis-ci.org/larsxschneider/git/jobs/125506786

Thanks,
Lars