iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/scripts/ci/build_and_test.sh

35 lines
1.0 KiB
Bash
Raw Normal View History

refactor(build): support multiple configurable browsers for e2e and perf tests Also includes browser configuration for Android
2015-01-08 17:20:05 -05:00
#!/bin/bash
build(ci): turn on debugging output for ci scripts Closes #5018
2015-11-05 11:20:13 -05:00
set -ex
refactor(build): support multiple configurable browsers for e2e and perf tests Also includes browser configuration for Android
2015-01-08 17:20:05 -05:00
chore(build): split Dart and JS builds
2015-02-13 17:59:29 -05:00
MODE=$1
refactor(build): support multiple configurable browsers for e2e and perf tests Also includes browser configuration for Android
2015-01-08 17:20:05 -05:00
echo =============================================================================
# go to project dir
SCRIPT_DIR=$(dirname $0)
cd $SCRIPT_DIR/../..
chore(ddc): make DDC build non-experimental
2016-01-26 01:47:42 -05:00
if [ "$MODE" = "dart_ddc" ]; then
chore(build): add experimental Dart build that uses DDC for code analysis
2015-06-03 20:22:30 -04:00
${SCRIPT_DIR}/build_$MODE.sh
build(sauce/bs): make some browsers required in CI Closes #5795
2015-12-10 08:40:00 -05:00
elif [[ $MODE = saucelabs* ]] ; then
${SCRIPT_DIR}/test_saucelabs.sh $MODE
elif [[ $MODE = browserstack* ]] ; then
${SCRIPT_DIR}/test_browserstack.sh $MODE
chore(build): faster feedback for broken lint Originally we ran gulp enforce-format at the beginning of the build. This was annoying because you came back from lunch to find that no tests ran so you have to start your PR over. Then we changed it to run the linters at the end. This is annoying because you might be ready to merge to master, and could have fixed the lint issues immediately, but now much wait for another PR. The solution is to run the lint checks in another build. This marks your PR red very early, but you still get the feedback of whether the tests are passing.
2015-07-29 20:00:54 -04:00
elif [ "$MODE" = "lint" ]; then
./node_modules/.bin/gulp static-checks
chore(travis): upload dist folder anytime the js and dart builds succeed Closes #5033
2015-10-30 10:34:48 -04:00
elif [ "$MODE" = "build_only" ]; then
${SCRIPT_DIR}/build_js.sh
${SCRIPT_DIR}/build_dart.sh
ci(typescript): add typescript_next build Install typescript@next before build.js and test.typings. Restore the regular version before travis caches node_modules/. Fixes #6368
2016-02-08 16:23:12 -05:00
elif [ "$MODE" = "typescript_next" ]; then
# Ignore complaints about unsatisfied peer deps
npm install typescript@next || true
${SCRIPT_DIR}/build_js.sh
./node_modules/.bin/gulp test.typings
chore(analytics): Travis job testing Dart payload size Add a job to the Travis build matrix that checks the size of the `hello_world` app against targets hard-coded in the gulpfile. Closes #5314
2015-11-20 12:59:08 -05:00
elif [ "$MODE" = "payload" ]; then
source ${SCRIPT_DIR}/env_dart.sh
./node_modules/.bin/gulp test.payload.dart/ci
chore: track size of a "Hello world" app built with SystemJS Closes #6621
2016-01-20 11:56:00 -05:00
node --max-old-space-size=2000 ./node_modules/.bin/gulp test.payload.js/ci
chore(build): add experimental Dart build that uses DDC for code analysis
2015-06-03 20:22:30 -04:00
else
chore(build): faster feedback for broken lint Originally we ran gulp enforce-format at the beginning of the build. This was annoying because you came back from lunch to find that no tests ran so you have to start your PR over. Then we changed it to run the linters at the end. This is annoying because you might be ready to merge to master, and could have fixed the lint issues immediately, but now much wait for another PR. The solution is to run the lint checks in another build. This marks your PR red very early, but you still get the feedback of whether the tests are passing.
2015-07-29 20:00:54 -04:00
${SCRIPT_DIR}/build_$MODE.sh
${SCRIPT_DIR}/test_$MODE.sh
chore(build): add experimental Dart build that uses DDC for code analysis
2015-06-03 20:22:30 -04:00
fi