neovim/ci/install.sh

#!/usr/bin/env bash

set -e
set -o pipefail

if [[ "${CI_TARGET}" == lint ]]; then
  python -m pip -q install --user --upgrade flake8
  exit
fi

if [[ "${TRAVIS_OS_NAME}" == osx ]]; then
  export PATH="/usr/local/opt/ccache/libexec:$PATH"
fi

# Use default CC to avoid compilation problems when installing Python modules.
echo "Install neovim module for Python 3."
CC=cc python3 -m pip -q install --upgrade pynvim
echo "Install neovim module for Python 2."
CC=cc python2 -m pip -q install --upgrade pynvim

echo "Install neovim RubyGem."
gem install --no-document --version ">= 0.8.0" neovim

echo "Install neovim npm package"
npm install -g neovim
npm link neovim
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: Check for exact value of CI_TARGET, not its emptyness 2017-03-31 07:39:18 -07:00			`if [[ "${CI_TARGET}" == lint ]]; then`
ci: pylint target via flake8 Ref: https://github.com/neovim/neovim/pull/10631#issuecomment-515756591 2019-07-28 20:04:12 -07:00			`python -m pip -q install --user --upgrade flake8`
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`
			`fi`

			`if [[ "${TRAVIS_OS_NAME}" == osx ]]; then`
travis: Enable ccache 2018-05-01 04:02:11 -07:00			`export PATH="/usr/local/opt/ccache/libexec:$PATH"`
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`

ci: Travis: simplify/improve Python/pip setup (#10228) * ci/before_install.sh: do not (try to) upgrade pip It is not necessary usually (for our use case(s)), and rather good to have this (implicitly) pinned. * Simplify/improve Python info output * Use pyenv-global to activate/use Python 2.7/7.7 * simplify pip-install of neovim, also for osx 2019-06-18 11:13:47 -07:00			`# Use default CC to avoid compilation problems when installing Python modules.`
Travis: Install Python 3 to run Python 3 tests. Install Python 3.3 from the Deadsnakes PPA. As this doesn't have pip, install it manually into ~/.local. ~/.local/bin is apparently in Travis's default PATH, meaning "pip" doesn't refer to Python 2's pip anymore, but to the manually installed Python 3 version. Updated the scripts to use version- suffixed executable names (e.g. pip2.7). Set CC=cc to use system's default compiler when installing Python modules, as gcc on OS X had a problem with compiling one of the dependencies of the Neovim Python module. 2015-09-22 05:36:15 -07:00			`echo "Install neovim module for Python 3."`
ci/travis: install pynvim outside of $HOME This runs the python tests on Travis. WIP: skip failing python tests 2019-09-14 14:29:31 -07:00			`CC=cc python3 -m pip -q install --upgrade pynvim`
ci: Travis: simplify/improve Python/pip setup (#10228) * ci/before_install.sh: do not (try to) upgrade pip It is not necessary usually (for our use case(s)), and rather good to have this (implicitly) pinned. * Simplify/improve Python info output * Use pyenv-global to activate/use Python 2.7/7.7 * simplify pip-install of neovim, also for osx 2019-06-18 11:13:47 -07:00			`echo "Install neovim module for Python 2."`
ci/travis: install pynvim outside of $HOME This runs the python tests on Travis. WIP: skip failing python tests 2019-09-14 14:29:31 -07:00			`CC=cc python2 -m pip -q install --upgrade pynvim`
ci: nodejs client acceptance-test #7706 ci: install nodejs 8 in Appveyor, Travis provider: check node version for debug support Resolve https://github.com/neovim/neovim/pull/7577#issuecomment-350590592 for Unix. provider: test if nodejs in ci supports --inspect-brk nodejs host for neovim requires nodejs 6+ to work properly. nodejs 6.12+ or 7.6+ is required for debug support via `node --inspect-brk`. provider: run cli.js of nodejs host directly npm shims are useless because the user cannot set node to debug mode via --inspect-brk. This is problematic on Windows which use batchfiles and shell scripts to compensate for not supporting shebang. The patch uses `npm root -g` to get the absolute path of the global npm modules. If that fails, then the user did not install neovim npm package globally. Use that absolute path to find `neovim/bin/cli.js`, which is what the npm shim actually runs with node. glob() is for a simple file check in case bin/ is removed because the npm shims are ignored now. 2017-11-28 23:50:11 -07:00
ci: install neovim gem on macOS High Sierra has ruby 2.3 preinstalled so neovim gem should work. 2018-12-27 07:44:52 -07:00			`echo "Install neovim RubyGem."`
			`gem install --no-document --version ">= 0.8.0" neovim`

ci/travis: install neovim npm module on osx (#7825) Always get latest nvm on osx to fix lts aliases. 2018-01-07 16:37:31 -07:00			`echo "Install neovim npm package"`
			`npm install -g neovim`
test: give more time for nodejs Link neovim package to project root directory. Increase delay to 3 seconds. Reduce the total lines in temporary node scripts. 2018-06-04 16:42:26 -07:00			`npm link neovim`