neovim/.ci/script.sh

#!/usr/bin/env bash

set -e
set -o pipefail

if [[ -n "${CI_TARGET}" ]]; then
  make "${CI_TARGET}"
  exit 0
fi

# This will pass the environment variables down to a bash process which runs
# as $USER, while retaining the environment variables defined and belonging
# to secondary groups given above in usermod.
if [[ "${TRAVIS_OS_NAME}" == osx ]]; then
  sudo -E su "${USER}" -c ".ci/run_tests.sh"
else
  .ci/run_tests.sh
fi
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching 2015-07-05 00:52:36 -07:00			`#!/usr/bin/env bash`

			`set -e`
			`set -o pipefail`

			`if [[ -n "${CI_TARGET}" ]]; then`
test: change CI_TARGET reference to CI Travis defines[1] $CI for its builds, whereas $CI_TARGET is a Neovim-specific env var from 6483a198e4bee1e80683ba12e061616c3e6c4090 that lost prominence in d2eb4a934683b5da63000d8b79a0d4c9a314d1c0. [1] https://docs.travis-ci.com/user/environment-variables/ 2016-01-01 21:58:42 -07:00			`make "${CI_TARGET}"`
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching 2015-07-05 00:52:36 -07:00			`exit 0`
			`fi`

			`# This will pass the environment variables down to a bash process which runs`
			`# as $USER, while retaining the environment variables defined and belonging`
			`# to secondary groups given above in usermod.`
			`if [[ "${TRAVIS_OS_NAME}" == osx ]]; then`
			`sudo -E su "${USER}" -c ".ci/run_tests.sh"`
			`else`
			`.ci/run_tests.sh`
			`fi`