vim/UltiSnips
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
411d0118ef
UltiSnips/.travis.yml

35 lines
1.7 KiB
YAML
Raw Normal View History

Move travis testing into docker for better consistency. (#950) This now only tests python2 on Vim 7.4, 8.0 and git. No Neovim (that has been broken for a long time anyways) and no longer any python3 testing. But hey, we have green tests again!
2018-03-31 18:56:34 -04:00
sudo: required
services: docker
# Cache intermediate Docker layers. For a description of how this works, see:
# https://giorgos.sealabs.net/docker-cache-on-travis-and-docker-112.html
cache:
directories:
- /home/travis/docker/
A travis script.
2015-02-14 08:38:17 -05:00
Started to test py2 and py3 on travis now. I also learned that Vim 7.3 does not seem to be working at all anymore. Fixes a bug that only happens with python3.
2015-04-18 11:15:05 -04:00
env:
Use a GitHub access token to avoid rate limiting of API. (#961) This will not help pull requests, as they are considered untrusted by Travis. But at least master builds and pull requests from branches in this repo should not hit rate limiting now.
2018-04-09 06:51:34 -04:00
matrix:
Move travis testing into docker for better consistency. (#950) This now only tests python2 on Vim 7.4, 8.0 and git. No Neovim (that has been broken for a long time anyways) and no longer any python3 testing. But hey, we have green tests again!
2018-03-31 18:56:34 -04:00
- VIM_VERSION="7.4" PYTHON_IMAGE=2.7-stretch TAG=vim_74_py2 DOCKER_CACHE_FILE=/home/travis/docker/vim_74_py2.tar.gz
- VIM_VERSION="8.0" PYTHON_IMAGE=2.7-stretch TAG=vim_80_py2 DOCKER_CACHE_FILE=/home/travis/docker/vim_80_py2.tar.gz
- VIM_VERSION="git" PYTHON_IMAGE=2.7-stretch TAG=vim_git_py2 DOCKER_CACHE_FILE=/home/travis/docker/vim_git_py2.tar.gz
Enable testing for python3 too. (#955) This gives us back testing parity to before CI broke - and hooray, all tests still pass!
2018-04-01 14:50:03 -04:00
- VIM_VERSION="7.4" PYTHON_IMAGE=3.6-stretch TAG=vim_74_py3 DOCKER_CACHE_FILE=/home/travis/docker/vim_74_py3.tar.gz
- VIM_VERSION="8.0" PYTHON_IMAGE=3.6-stretch TAG=vim_80_py3 DOCKER_CACHE_FILE=/home/travis/docker/vim_80_py3.tar.gz
- VIM_VERSION="git" PYTHON_IMAGE=3.6-stretch TAG=vim_git_py3 DOCKER_CACHE_FILE=/home/travis/docker/vim_git_py3.tar.gz
Use a GitHub access token to avoid rate limiting of API. (#961) This will not help pull requests, as they are considered untrusted by Travis. But at least master builds and pull requests from branches in this repo should not hit rate limiting now.
2018-04-09 06:51:34 -04:00
global:
secure: PFU1Md8NuN6SQNjx6SsHX7icS9Tacb0xS0Ue9SHll1U7FNdI90F/gnokR6v+j7sdvoiLkwRSwUXeYUmrZS/d9qq8yiRxuqcj/Y0TfHVKqcLXXV/m9xWAN2UKRVF7Z1neerznk52Roo3IRqwgd9U+6d3bTthHKKYg4azBqTM7AFE=
Rename scripts -> docker. Make repro more useful.
2018-04-05 15:52:33 -04:00
before_install: docker/load_docker_cache.sh
Fix testing and test against more scenarios. Before this, we only ever ran against system python preinstalled on travis (i.e. 2.7 and 3.2). This change makes sure that Vim is always build and run against the correct python version in the virtual env. Also adds mercurial (HEAD) Vim as a testing target. This patch took me forever to get right. At least 2 months and ~200 travis runs of trial and error - there is just too much finicky going on with the many virtual envs on travis, Vims strange build system that does not use python-config and LD_LIBRARY_PATH loading. En plus, the debugging insights one can glance from travis runs are rather limited. Detailed changes: - Uses less sudo and only outside of scripts. - Build correct version of Vim against correct version of Python. This needs some LD_LIBRARY_PATH magic to make sure that Vim finds the correct Python libraries at runtime. - Removes dirty hack that overwrote /usr/bin/vim with the correct Vim version to run. The test_all.py script now takes the Vim binary as a parameter.
2015-07-03 15:52:50 -04:00
install:
Use a GitHub access token to avoid rate limiting of API. (#961) This will not help pull requests, as they are considered untrusted by Travis. But at least master builds and pull requests from branches in this repo should not hit rate limiting now.
2018-04-09 06:51:34 -04:00
- docker build -t ultisnips:${TAG} --build-arg PYTHON_IMAGE=${PYTHON_IMAGE} --build-arg VIM_VERSION=${VIM_VERSION} --build-arg GITHUB_ACCESS_TOKEN=${GITHUB_ACCESS_TOKEN} .
Started to test py2 and py3 on travis now. I also learned that Vim 7.3 does not seem to be working at all anymore. Fixes a bug that only happens with python3.
2015-04-18 11:15:05 -04:00
Fix testing and test against more scenarios. Before this, we only ever ran against system python preinstalled on travis (i.e. 2.7 and 3.2). This change makes sure that Vim is always build and run against the correct python version in the virtual env. Also adds mercurial (HEAD) Vim as a testing target. This patch took me forever to get right. At least 2 months and ~200 travis runs of trial and error - there is just too much finicky going on with the many virtual envs on travis, Vims strange build system that does not use python-config and LD_LIBRARY_PATH loading. En plus, the debugging insights one can glance from travis runs are rather limited. Detailed changes: - Uses less sudo and only outside of scripts. - Build correct version of Vim against correct version of Python. This needs some LD_LIBRARY_PATH magic to make sure that Vim finds the correct Python libraries at runtime. - Removes dirty hack that overwrote /usr/bin/vim with the correct Vim version to run. The test_all.py script now takes the Vim binary as a parameter.
2015-07-03 15:52:50 -04:00
script:
Rename scripts -> docker. Make repro more useful.
2018-04-05 15:52:33 -04:00
- docker run -it ultisnips:${TAG} docker/run_tests.sh
- docker/save_docker_cache.sh
Add a webhook for gitter.im.
2015-07-18 16:53:41 -04:00
notifications:
webhooks:
urls:
- https://webhooks.gitter.im/e/558acac434012ba838cd
on_success: change # options: [always|never|change] default: always
on_failure: always # options: [always|never|change] default: always
on_start: false # default: false
Reference in New Issue Copy Permalink