angular-cn/scripts/ci/build_and_test.sh

#!/bin/bash
set -e

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" ]; then
  ${SCRIPT_DIR}/test_$MODE.sh
elif [ "$MODE" = "lint" ]; then
  ./node_modules/.bin/gulp static-checks
else
  ${SCRIPT_DIR}/build_$MODE.sh
  mkdir deploy; tar -czpf deploy/dist.tgz -C dist .
  ${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 17:20:05 -05:00			`#!/bin/bash`
			`set -e`

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(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			`if [ "$MODE" = "dart_experimental" ]; 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`
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" = "saucelabs" ]; then`
			`${SCRIPT_DIR}/test_$MODE.sh`
			`elif [ "$MODE" = "lint" ]; then`
			`./node_modules/.bin/gulp static-checks`
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`
			`mkdir deploy; tar -czpf deploy/dist.tgz -C dist .`
			`${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`