Skip to content
Permalink
Browse files

chore: use yarn to run commands on CI to make output better

  • Loading branch information
MarshallOfSound committed Sep 10, 2018
1 parent 640ba77 commit 12209b00d9182162474923f51c17d43cf7b02b36
Showing with 7 additions and 7 deletions.
  1. +3 −3 .appveyor.yml
  2. +4 −4 ci/script.sh
@@ -19,7 +19,7 @@ install:
- if not exist "node_modules" mkdir node_modules
- ps: Remove-Item node_modules -Recurse -Force
- bolt
- bolt build
- yarn build
- ps: |
$wixToolsetBinPath = ";C:\Program Files (x86)\WiX Toolset v3.11\bin;"
$env:PATH = $env:PATH + $wixToolsetBinPath
@@ -32,7 +32,7 @@ install:
test_script:
- node --version
- yarn --version
- bolt lint
- bolt test
- yarn lint
- yarn test

build: off
@@ -6,12 +6,12 @@ if [[ "$TRAVIS_OS_NAME" = "linux" ]]; then
sudo docker run --privileged --interactive --tty --volume $(pwd):/code malept/electron-forge-container:latest /code/ci/docker.sh $NODE_INSTALLER
else
bolt
bolt build
bolt lint
bolt ws test
yarn build
yarn lint
yarn test
echo "$NODE_INSTALLER-$TRAVIS_SECURE_ENV_VARS-$TRAVIS_BRANCH"
if [[ "$NODE_INSTALLER-$TRAVIS_SECURE_ENV_VARS-$TRAVIS_BRANCH" = "yarn-true-master" ]]; then
npm i -g now
bolt docs:deploy:ci
yarn docs:deploy:ci
fi
fi

0 comments on commit 12209b0

Please sign in to comment.
You can’t perform that action at this time.