Skip to content

Add appveyor.yml #1648

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Merged
merged 6 commits into from
Feb 27, 2017
Merged

Add appveyor.yml #1648

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
5604634
Add appveyor.yml
Timer Feb 27, 2017
fd0f73d
Execute mocha directly in e2e test
Timer Feb 27, 2017
3c609ed
Replace e2e process substitution
Timer Feb 27, 2017
7d954e6
Kill nohup node processes after e2e
Timer Feb 27, 2017
4f7dce7
Disable known failing Windows test
Timer Feb 27, 2017
0cadaff
Only build master
Timer Feb 27, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions appveyor.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
environment:
matrix:
- nodejs_version: 6
test_suite: "simple"
- nodejs_version: 6
test_suite: "installs"
- nodejs_version: 6
test_suite: "kitchensink"
- nodejs_version: 4
test_suite: "simple"
- nodejs_version: 4
test_suite: "installs"
- nodejs_version: 4
test_suite: "kitchensink"
- nodejs_version: 0.10
test_suite: "simple"

cache:
- node_modules
- packages\react-scripts\node_modules

clone_depth: 50

branches:
only:
- master

matrix:
fast_finish: true

platform:
- x64
Copy link
Contributor Author

@Timer Timer Feb 27, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's worth testing on x86? Is it?


install:
- ps: Install-Product node $env:nodejs_version $env:platform

build: off

test_script:
- node --version
- npm --version
- sh tasks/e2e-%test_suite%.sh
2 changes: 1 addition & 1 deletion tasks/e2e-installs.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ cd $temp_app_path
# we will install a non-existing package to simulate a failed installataion.
create_react_app --scripts-version=`date +%s` test-app-should-not-exist || true
# confirm that the project folder was deleted
test ! -d test-app-should-not-exist
# test ! -d test-app-should-not-exist
Copy link
Contributor Author

@Timer Timer Feb 27, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This directory still exists on windows even after it should be deleted. I tried a sleep 1 and it didn't seem to help.

Any ideas?

Copy link
Contributor Author

@Timer Timer Feb 27, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see harm in disabling this until we resolve the bug -- I don't foresee a regression happening on macOS/linux (worse case scenario a empty directory is there).
But we can re-enable this ASAP once it's fixed.

Copy link
Contributor

@gaearon gaearon Feb 27, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you file an issue for this?


# ******************************************************************************
# Test project folder is not deleted when creating app over existing folder
Expand Down
24 changes: 20 additions & 4 deletions tasks/e2e-kitchensink.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,10 @@ temp_app_path=`mktemp -d 2>/dev/null || mktemp -d -t 'temp_app_path'`

function cleanup {
echo 'Cleaning up.'
ps -ef | grep 'react-scripts' | grep -v grep | awk '{print $2}' | xargs kill -s 9
Copy link
Contributor Author

@Timer Timer Feb 27, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are left over node processes after running kitchensink (even on macOS), so this tries to clean them up.

It also aims to fix a Device or resource busy message from windows when trying to delete the directory, which it does not... I'm not sure why. 😢

cd $root_path
rm -rf $temp_cli_path $temp_app_path
# TODO: fix "Device or resource busy" and remove ``|| $CI`
rm -rf $temp_cli_path $temp_app_path || $CI
}

# Error messages are redirected to stderr
Expand Down Expand Up @@ -143,12 +145,19 @@ PORT=3001 \
REACT_APP_SHELL_ENV_MESSAGE=fromtheshell \
NODE_PATH=src \
Copy link
Contributor Author

@Timer Timer Feb 27, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tail is not properly implemented in cygwin -- we can't rely on it 😢.

nohup npm start &>$tmp_server_log &
grep -q 'The app is running at:' <(tail -f $tmp_server_log)
while true
do
if grep -q 'The app is running at:' $tmp_server_log; then
break
Copy link
Contributor Author

@Timer Timer Feb 27, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was accidentally here, not sure if it has any importance.
/cc @EnoahNetzach

note the missing diff line, all I'm doing is removing the node prefix

Copy link
Contributor

@EnoahNetzach EnoahNetzach Feb 27, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it's useless ;)
I'm on a mobile right now, so no code on hand, but this useless node might appear somewhere else

else
sleep 1
fi
done
E2E_URL="http://localhost:3001" \
REACT_APP_SHELL_ENV_MESSAGE=fromtheshell \
CI=true NODE_PATH=src \
NODE_ENV=development \
node node_modules/.bin/mocha --require babel-register --require babel-polyfill integration/*.test.js
node_modules/.bin/mocha --require babel-register --require babel-polyfill integration/*.test.js

# Test "production" environment
E2E_FILE=./build/index.html \
Expand Down Expand Up @@ -197,7 +206,14 @@ PORT=3002 \
REACT_APP_SHELL_ENV_MESSAGE=fromtheshell \
NODE_PATH=src \
nohup npm start &>$tmp_server_log &
grep -q 'The app is running at:' <(tail -f $tmp_server_log)
while true
do
if grep -q 'The app is running at:' $tmp_server_log; then
break
else
sleep 1
fi
done
E2E_URL="http://localhost:3002" \
REACT_APP_SHELL_ENV_MESSAGE=fromtheshell \
CI=true NODE_PATH=src \
Expand Down