kevin/neovim
1
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2024-12-29 14:41:06 -07:00
Code Issues Packages Projects Releases Wiki Activity
8a8213f6d4
neovim/appveyor.yml

35 lines
957 B
YAML
Raw Normal View History

Windows: Crank to MSVC 2015 on AppVeyor. #3254
2015-08-27 14:09:21 -07:00
version: '{build}'
ci/appveyor: modify compression options for cache Attempt to workaround #7317 by using a different compression algorithm.
2017-09-30 07:06:13 -07:00
environment:
APPVEYOR_CACHE_ENTRY_ZIP_ARGS: "-t7z -m0=lzma -mx=9"
CI/AppVeyor: build deps out-of-tree appveyor.yml: set cache to an absolute path. Desperate attempt to get AppVeyor cache to work. My assumption in a7a56293aad9 #9852 that that different jobs were overwriting each other's cache is probably wrong: AppVeyor docs/discussions hint that the cache is per-config (though I haven't found a clear, unambiguous statement as such).
2019-04-07 15:14:01 -07:00
DEPS_BUILD_DIR: "C:/projects/nvim-deps"
DEPS_PREFIX: "C:/projects/nvim-deps/usr"
build/msvc: Add Appveyor CI for MSVC
2018-03-04 16:44:23 -07:00
image: Visual Studio 2017
build: Refactor appveyor/Windows scripts (#5244) - Join all msys build scripts into one - Clean up appveyor.yml and generate installer for tagged builds A side effect of the cosmetic changes is that appveyor artifact permalinks are easier to use, e.g. for the latest zip in the master branch https://ci.appveyor.com/api/projects/neovim/neovim/artifacts/build/Neovim.zip?branch=master&job=Configuration%3A%20MINGW_64
2016-08-25 22:38:46 -07:00
configuration:
ci/AppVeyor: enable MSVC_32 build
2018-03-26 08:54:44 -07:00
- MSVC_64
- MSVC_32
build: Refactor appveyor/Windows scripts (#5244) - Join all msys build scripts into one - Clean up appveyor.yml and generate installer for tagged builds A side effect of the cosmetic changes is that appveyor artifact permalinks are easier to use, e.g. for the latest zip in the master branch https://ci.appveyor.com/api/projects/neovim/neovim/artifacts/build/Neovim.zip?branch=master&job=Configuration%3A%20MINGW_64
2016-08-25 22:38:46 -07:00
- MINGW_64
- MINGW_32
ci/win: list build permutations explicitly (#7163) This avoids changing the matrix permutations for the old non-gcov builds, so that old URLs continue to work: https://ci.appveyor.com/api/projects/neovim/neovim/artifacts/build/Neovim.zip?branch=master&job=Configuration%3A%20MINGW_32 https://ci.appveyor.com/api/projects/neovim/neovim/artifacts/build/Neovim.zip?branch=master&job=Configuration%3A%20MINGW_64
2017-08-15 02:06:51 -07:00
- MINGW_64-gcov
CI/AppVeyor: do skip-logic earlier #9854
2019-04-07 05:43:50 -07:00
init:
- ps: |
# For pull requests, skip some build configurations to save time.
if ($env:APPVEYOR_PULL_REQUEST_HEAD_COMMIT -and $env:CONFIGURATION -match '^(MSVC_64|MINGW_32|MINGW_64-gcov)$') {
$env:APPVEYOR_CACHE_SKIP_SAVE = "true"
Exit-AppVeyorBuild
}
CI/AppVeyor: build deps out-of-tree appveyor.yml: set cache to an absolute path. Desperate attempt to get AppVeyor cache to work. My assumption in a7a56293aad9 #9852 that that different jobs were overwriting each other's cache is probably wrong: AppVeyor docs/discussions hint that the cache is per-config (though I haven't found a clear, unambiguous statement as such).
2019-04-07 15:14:01 -07:00
# RDP
#- ps: iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-rdp.ps1'))
ci: Ignore MINGW_64-gcov failures in overall ci status
2017-08-16 08:24:12 -07:00
matrix:
allow_failures:
- configuration: MINGW_64-gcov
Windows: Crank to MSVC 2015 on AppVeyor. #3254
2015-08-27 14:09:21 -07:00
install: []
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
before_build:
- ps: Install-Product node 8
Windows: Crank to MSVC 2015 on AppVeyor. #3254
2015-08-27 14:09:21 -07:00
build_script:
ci/AppVeyor: use PowerShell (#8124)
2018-03-11 15:44:07 -07:00
- powershell ci\build.ps1
win/CI: Cache dependencies.
2017-02-15 19:10:00 -07:00
cache:
CI/AppVeyor: build deps out-of-tree appveyor.yml: set cache to an absolute path. Desperate attempt to get AppVeyor cache to work. My assumption in a7a56293aad9 #9852 that that different jobs were overwriting each other's cache is probably wrong: AppVeyor docs/discussions hint that the cache is per-config (though I haven't found a clear, unambiguous statement as such).
2019-04-07 15:14:01 -07:00
- C:\projects\nvim-deps -> third-party\**
Appveyor: Generate helptags and build artifacts Build the default CMake target now that helptag generation is working again. For build artifacts create a zip file with an instalation of Neovim (generated by cpack).
2016-08-01 05:16:08 -07:00
artifacts:
- path: build/Neovim.zip
ci: Update appveyor artifact path.
2016-12-09 08:36:16 -07:00
- path: build/bin/nvim.exe
Reference in New Issue Copy Permalink