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

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

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Apr 22, 2016, 09:07 UTC
Message-ID
<vpq37qeovu4.fsf@anie.imag.fr>
In-Reply-To
<1461314042-3132-1-git-send-email-larsxschneider@gmail.com>
larsxschneider@gmail.com writes:
> +      if [[ "$TRAVIS_OS_NAME" = linux ]] && [[ "$CC" = gcc ]];

[[ is a bashism, and doesn't bring anything here compared to the POSIX [ ... ], or "test" which is prefered in Git's source code.

The ; or the newline is not needed either.
I'd write
if test "$TRAVIS_OS_NAME" = linux && test "$CC" = gcc; then
> +          then
> +          echo ""
> +          echo "------------------------------------------------------------------------" &&

I usualy avoid "echo <something-starting-with-dash>" as I'm not sure how portable it is across variants of "echo". Maybe this one is portable enough, I don't know. Perhaps printf, or cat << EOF ...?

> +          echo "$(tput setaf 2)Building documentation...$(tput sgr0)" &&
> +          make --quiet doc
> +      fi;
Nit: useless ;

I think it makes sense to do some lightweight checks after "make doc", rather than just check the return code. For example, check that a few generated files exist and are non-empty, like

test -s Documentation/git.html && test -s Documentation/git.1

Thanks,
-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: larsxschneider@gmail.comNext: Junio C Hamano
Message 2 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.