2017-04-26 21:15:44 +02:00
|
|
|
#!/usr/bin/env bash
|
2016-05-04 10:38:36 +02:00
|
|
|
#
|
|
|
|
|
# Perform sanity checks on documentation and build it.
|
|
|
|
|
#
|
|
|
|
|
|
2017-09-10 16:44:28 +02:00
|
|
|
. ${0%/*}/lib-travisci.sh
|
|
|
|
|
|
|
|
|
|
gem install asciidoctor
|
2016-05-04 10:38:36 +02:00
|
|
|
|
|
|
|
|
make check-builtins
|
|
|
|
|
make check-docs
|
|
|
|
|
|
2017-04-11 10:33:07 +02:00
|
|
|
# Build docs with AsciiDoc
|
2017-04-26 21:15:44 +02:00
|
|
|
make --jobs=2 doc > >(tee stdout.log) 2> >(tee stderr.log >&2)
|
|
|
|
|
! test -s stderr.log
|
2016-05-04 10:38:36 +02:00
|
|
|
test -s Documentation/git.html
|
|
|
|
|
test -s Documentation/git.xml
|
|
|
|
|
test -s Documentation/git.1
|
2017-04-11 10:33:07 +02:00
|
|
|
grep '<meta name="generator" content="AsciiDoc ' Documentation/git.html
|
|
|
|
|
|
2017-12-31 17:02:06 +01:00
|
|
|
rm -f stdout.log stderr.log
|
|
|
|
|
check_unignored_build_artifacts
|
|
|
|
|
|
2017-04-11 10:33:07 +02:00
|
|
|
# Build docs with AsciiDoctor
|
|
|
|
|
make clean
|
2017-04-26 21:15:44 +02:00
|
|
|
make --jobs=2 USE_ASCIIDOCTOR=1 doc > >(tee stdout.log) 2> >(tee stderr.log >&2)
|
|
|
|
|
sed '/^GIT_VERSION = / d' stderr.log
|
|
|
|
|
! test -s stderr.log
|
2017-04-11 10:33:07 +02:00
|
|
|
test -s Documentation/git.html
|
|
|
|
|
grep '<meta name="generator" content="Asciidoctor ' Documentation/git.html
|
travis-ci: record and skip successfully built trees
Travis CI dutifully builds and tests each new branch tip, even if its
tree has previously been successfully built and tested. This happens
often enough in contributors' workflows, when a work-in-progress
branch is rebased changing e.g. only commit messages or the order or
number of commits while leaving the resulting code intact, and is then
pushed to a Travis CI-enabled GitHub fork.
This is wasting Travis CI's resources and is sometimes scary-annoying
when the new tip commit with a tree identical to the previous,
successfully tested one is suddenly reported in red, because one of
the OSX build jobs happened to exceed the time limit yet again.
So extend our Travis CI build scripts to skip building commits whose
trees have previously been successfully built and tested. Use the
Travis CI cache feature to keep a record of the object names of trees
that tested successfully, in a plain and simple flat text file, one
line per tree object name. Append the current tree's object name at
the end of every successful build job to this file, along with a bit
of additional info about the build job (commit object name, Travis CI
job number and id). Limit the size of this file to 1000 records, to
prevent it from growing too large for git/git's forever living
integration branches. Check, using a simple grep invocation, in each
build job whether the current commit's tree is already in there, and
skip the build if it is. Include a message in the skipped build job's
trace log, containing the URL to the build job successfully testing
that tree for the first time and instructions on how to force a
re-build. Catch the case when a build job, which successfully built
and tested a particular tree for the first time, is restarted and omit
the URL of the previous build job's trace log, as in this case it's
the same build job and the trace log has just been overwritten.
Note: this won't kick in if two identical trees are on two different
branches, because Travis CI caches are not shared between build jobs
of different branches.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Reviewed-by: Lars Schneider <larsxschneider@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-12-31 11:12:05 +01:00
|
|
|
|
2017-12-31 17:02:06 +01:00
|
|
|
rm -f stdout.log stderr.log
|
|
|
|
|
check_unignored_build_artifacts
|
|
|
|
|
|
travis-ci: record and skip successfully built trees
Travis CI dutifully builds and tests each new branch tip, even if its
tree has previously been successfully built and tested. This happens
often enough in contributors' workflows, when a work-in-progress
branch is rebased changing e.g. only commit messages or the order or
number of commits while leaving the resulting code intact, and is then
pushed to a Travis CI-enabled GitHub fork.
This is wasting Travis CI's resources and is sometimes scary-annoying
when the new tip commit with a tree identical to the previous,
successfully tested one is suddenly reported in red, because one of
the OSX build jobs happened to exceed the time limit yet again.
So extend our Travis CI build scripts to skip building commits whose
trees have previously been successfully built and tested. Use the
Travis CI cache feature to keep a record of the object names of trees
that tested successfully, in a plain and simple flat text file, one
line per tree object name. Append the current tree's object name at
the end of every successful build job to this file, along with a bit
of additional info about the build job (commit object name, Travis CI
job number and id). Limit the size of this file to 1000 records, to
prevent it from growing too large for git/git's forever living
integration branches. Check, using a simple grep invocation, in each
build job whether the current commit's tree is already in there, and
skip the build if it is. Include a message in the skipped build job's
trace log, containing the URL to the build job successfully testing
that tree for the first time and instructions on how to force a
re-build. Catch the case when a build job, which successfully built
and tested a particular tree for the first time, is restarted and omit
the URL of the previous build job's trace log, as in this case it's
the same build job and the trace log has just been overwritten.
Note: this won't kick in if two identical trees are on two different
branches, because Travis CI caches are not shared between build jobs
of different branches.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Reviewed-by: Lars Schneider <larsxschneider@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-12-31 11:12:05 +01:00
|
|
|
save_good_tree
|