neovim/ci/before_cache.sh

#!/usr/bin/env bash

set -e
set -o pipefail

CI_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
source "${CI_DIR}/common/suite.sh"

# Don't cache pip's log and selfcheck.
rm -rf "${HOME}/.cache/pip/log"
rm -f "${HOME}/.cache/pip/selfcheck.json"

# Update the third-party dependency cache only if the build was successful.
if ended_successfully; then
  rm -rf "${HOME}/.cache/nvim-deps"
  mv "${DEPS_BUILD_DIR}" "${HOME}/.cache/nvim-deps"
  touch "${CACHE_MARKER}"
  echo "Updated third-party dependencies (timestamp: $(stat -c '%y' "${CACHE_MARKER}"))."
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`

ci: Really continue tests on failure, print global summary 2017-04-04 10:15:30 -07:00			`CI_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"`
			`source "${CI_DIR}/common/suite.sh"`

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			`# Don't cache pip's log and selfcheck.`
			`rm -rf "${HOME}/.cache/pip/log"`
			`rm -f "${HOME}/.cache/pip/selfcheck.json"`

			`# Update the third-party dependency cache only if the build was successful.`
ci: Really continue tests on failure, print global summary 2017-04-04 10:15:30 -07:00			`if ended_successfully; then`
Travis: Cache third-party build directory. Instead of just caching the third-party build output, cache the full build directory. Always run make to ensure that updated dependencies are downloaded. 2015-09-08 03:48:04 -07:00			`rm -rf "${HOME}/.cache/nvim-deps"`
Travis: Enable before_cache script for MacOS. (#5007) Travis now seems to support caching on MacOS. 2016-07-04 17:51:34 -07:00			`mv "${DEPS_BUILD_DIR}" "${HOME}/.cache/nvim-deps"`
Travis: Cache third-party build directory. Instead of just caching the third-party build output, cache the full build directory. Always run make to ensure that updated dependencies are downloaded. 2015-09-08 03:48:04 -07:00			`touch "${CACHE_MARKER}"`
			`echo "Updated third-party dependencies (timestamp: $(stat -c '%y' "${CACHE_MARKER}"))."`
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			`fi`