We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As was pointed out by @bcoe in #55 it would be great to have AppVeyor run windows tests. Merging TravisCI and AppVeyor coverage is not so simple though (see lemurheavy/coveralls-public/issues/613). Suggested base config was https://github.com/yargs/yargs-parser/blob/master/appveyor.yml.
Some modifications:
nodejs_version: '0.10'
shallow_clone: true
clone_depth: 1
So that leaves us with:
# Fix line endings on Windows init: - git config --global core.autocrlf true environment: matrix: - nodejs_version: '6' - nodejs_version: '4' - nodejs_version: '0.12' - nodejs_version: '0.10' install: - ps: Install-Product node $env:nodejs_version - set CI=true - npm -g install npm@latest - set PATH=%APPDATA%\npm;%PATH% - npm install matrix: fast_finish: true build: off version: '{build}' test_script: - node --version - npm --version - npm test
On a related note, the travis.yml should probably include node version 4 as well as the latest (v6)?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As was pointed out by @bcoe in #55 it would be great to have AppVeyor run windows tests. Merging TravisCI and AppVeyor coverage is not so simple though (see lemurheavy/coveralls-public/issues/613).
Suggested base config was https://github.com/yargs/yargs-parser/blob/master/appveyor.yml.
Some modifications:
nodejs_version: '0.10'
as it is present in travis.yml as well.shallow_clone: true
andclone_depth: 1
? Removed them for now.So that leaves us with:
On a related note, the travis.yml should probably include node version 4 as well as the latest (v6)?
The text was updated successfully, but these errors were encountered: