angular-cn/scripts/ci/build_and_test.sh

#!/bin/bash
set -ex

MODE=$1

echo =============================================================================
# go to project dir
SCRIPT_DIR=$(dirname $0)
cd $SCRIPT_DIR/../..

if [ "$MODE" = "dart_experimental" ]; then
  ${SCRIPT_DIR}/build_$MODE.sh
elif [ "$MODE" = "saucelabs" ] || [ "$MODE" = "browserstack" ] ; then
  ${SCRIPT_DIR}/test_$MODE.sh
elif [ "$MODE" = "lint" ]; then
  ./node_modules/.bin/gulp static-checks
elif [ "$MODE" = "build_only" ]; then
  ${SCRIPT_DIR}/build_js.sh
  ${SCRIPT_DIR}/build_dart.sh
  mkdir deploy; tar -czpf deploy/dist.tgz -C dist .
elif [ "$MODE" = "payload" ]; then
  source ${SCRIPT_DIR}/env_dart.sh
  ./node_modules/.bin/gulp test.payload.dart/ci
else
  ${SCRIPT_DIR}/build_$MODE.sh
  ${SCRIPT_DIR}/test_$MODE.sh
fi
refactor(build): support multiple configurable browsers for e2e and perf tests Also includes browser configuration for Android 2015-01-08 14:20:05 -08:00			`#!/bin/bash`
build(ci): turn on debugging output for ci scripts Closes #5018 2015-11-05 08:20:13 -08:00			`set -ex`
refactor(build): support multiple configurable browsers for e2e and perf tests Also includes browser configuration for Android 2015-01-08 14:20:05 -08:00
chore(build): split Dart and JS builds 2015-02-13 14:59:29 -08:00			`MODE=$1`

refactor(build): support multiple configurable browsers for e2e and perf tests Also includes browser configuration for Android 2015-01-08 14:20:05 -08:00			`echo =============================================================================`
			`# go to project dir`
			`SCRIPT_DIR=$(dirname $0)`
			`cd $SCRIPT_DIR/../..`

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 17:00:54 -07:00			`if [ "$MODE" = "dart_experimental" ]; then`
chore(build): add experimental Dart build that uses DDC for code analysis 2015-06-03 17:22:30 -07:00			`${SCRIPT_DIR}/build_$MODE.sh`
build(browserstack): initial setup Closes #4941 2015-10-27 16:09:09 +01:00			`elif [ "$MODE" = "saucelabs" ] \|\| [ "$MODE" = "browserstack" ] ; then`
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 17:00:54 -07:00			`${SCRIPT_DIR}/test_$MODE.sh`
			`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 07:34:48 -07:00			`elif [ "$MODE" = "build_only" ]; then`
			`${SCRIPT_DIR}/build_js.sh`
			`${SCRIPT_DIR}/build_dart.sh`
			`mkdir deploy; tar -czpf deploy/dist.tgz -C dist .`
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 09:59:08 -08:00			`elif [ "$MODE" = "payload" ]; then`
			`source ${SCRIPT_DIR}/env_dart.sh`
			`./node_modules/.bin/gulp test.payload.dart/ci`
chore(build): add experimental Dart build that uses DDC for code analysis 2015-06-03 17:22:30 -07: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 17:00:54 -07: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 17:22:30 -07:00			`fi`