mirror of
https://github.com/git/git.git
synced 2024-11-18 02:04:08 +01:00
3c93b82920
Ever since we started building and testing Git on Travis CI (522354d70
(Add Travis CI support, 2015-11-27)), we build Git in the
'before_script' phase and run the test suite in the 'script' phase
(except in the later introduced 32 bit Linux and Windows build jobs,
where we build in the 'script' phase').
Contrarily, the Travis CI practice is to build and test in the
'script' phase; indeed Travis CI's default build command for the
'script' phase of C/C++ projects is:
./configure && make && make test
The reason why Travis CI does it this way and why it's a better
approach than ours lies in how unsuccessful build jobs are
categorized. After something went wrong in a build job, its state can
be:
- 'failed', if a command in the 'script' phase returned an error.
This is indicated by a red 'X' on the Travis CI web interface.
- 'errored', if a command in the 'before_install', 'install', or
'before_script' phase returned an error, or the build job exceeded
the time limit. This is shown as a red '!' on the web interface.
This makes it easier, both for humans looking at the Travis CI web
interface and for automated tools querying the Travis CI API, to
decide when an unsuccessful build is our responsibility requiring
human attention, i.e. when a build job 'failed' because of a compiler
error or a test failure, and when it's caused by something beyond our
control and might be fixed by restarting the build job, e.g. when a
build job 'errored' because a dependency couldn't be installed due to
a temporary network error or because the OSX build job exceeded its
time limit.
The drawback of building Git in the 'before_script' phase is that one
has to check the trace log of all 'errored' build jobs, too, to see
what caused the error, as it might have been caused by a compiler
error. This requires additional clicks and page loads on the web
interface and additional complexity and API requests in automated
tools.
Therefore, move building Git from the 'before_script' phase to the
'script' phase, updating the script's name accordingly as well.
'ci/run-builds.sh' now becomes basically empty, remove it. Several of
our build job configurations override our default 'before_script' to
do nothing; with this change our default 'before_script' won't do
anything, either, so remove those overriding directives as well.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
77 lines
1.3 KiB
YAML
77 lines
1.3 KiB
YAML
language: c
|
|
|
|
sudo: false
|
|
|
|
cache:
|
|
directories:
|
|
- $HOME/travis-cache
|
|
|
|
os:
|
|
- linux
|
|
- osx
|
|
|
|
compiler:
|
|
- clang
|
|
- gcc
|
|
|
|
addons:
|
|
apt:
|
|
packages:
|
|
- language-pack-is
|
|
- git-svn
|
|
- apache2
|
|
|
|
matrix:
|
|
include:
|
|
- env: jobname=GETTEXT_POISON
|
|
os: linux
|
|
compiler:
|
|
addons:
|
|
before_install:
|
|
- env: jobname=Windows
|
|
os: linux
|
|
compiler:
|
|
addons:
|
|
before_install:
|
|
script:
|
|
- >
|
|
test "$TRAVIS_REPO_SLUG" != "git/git" ||
|
|
ci/run-windows-build.sh $TRAVIS_BRANCH $(git rev-parse HEAD)
|
|
after_failure:
|
|
- env: jobname=Linux32
|
|
os: linux
|
|
compiler:
|
|
addons:
|
|
services:
|
|
- docker
|
|
before_install:
|
|
script: ci/run-linux32-docker.sh
|
|
- env: jobname=StaticAnalysis
|
|
os: linux
|
|
compiler:
|
|
addons:
|
|
apt:
|
|
packages:
|
|
- coccinelle
|
|
before_install:
|
|
script: ci/run-static-analysis.sh
|
|
after_failure:
|
|
- env: jobname=Documentation
|
|
os: linux
|
|
compiler:
|
|
addons:
|
|
apt:
|
|
packages:
|
|
- asciidoc
|
|
- xmlto
|
|
before_install:
|
|
script: ci/test-documentation.sh
|
|
after_failure:
|
|
|
|
before_install: ci/install-dependencies.sh
|
|
script: ci/run-build-and-tests.sh
|
|
after_failure: ci/print-test-failures.sh
|
|
|
|
notifications:
|
|
email: false
|