git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v1] travis-ci: build documentation

From
Lars Schneider <larsxschneider@gmail.com>
Date
Apr 25, 2016, 08:35 UTC
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:
Show 13 quoted lines
> 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

Previous: Jeff KingNext: Jeff King
Message 15 of 16 in “travis-ci: build documentation”
  1. travis-ci: build documentationlarsxschneider@gmail.com, Apr 22, 2016
  2. Matthieu MoyApr 22, 2016
  3. Junio C HamanoApr 22, 2016
  4. Lars SchneiderApr 25, 2016
  5. Junio C HamanoApr 25, 2016
  6. Junio C HamanoApr 25, 2016
  7. Matthieu MoyApr 25, 2016
  8. Junio C HamanoApr 25, 2016
  9. Matthieu MoyApr 25, 2016
  10. Lars SchneiderApr 25, 2016
  11. Matthieu MoyApr 25, 2016
  12. stefan.naewe@atlas-elektronik.comApr 22, 2016
  13. Lars SchneiderApr 25, 2016
  14. Jeff KingApr 23, 2016
  15. Lars SchneiderApr 25, 2016
  16. Jeff KingApr 25, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.