angular-cn/scripts/ci/build_js.sh

#!/bin/bash
set -e

echo =============================================================================
# go to project dir
SCRIPT_DIR=$(dirname $0)
# this is needed because we're running JS tests in Dartium too
source $SCRIPT_DIR/env_dart.sh
cd $SCRIPT_DIR/../..

./node_modules/.bin/gulp enforce-format build.js docs
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`

			`echo =============================================================================`
			`# go to project dir`
			`SCRIPT_DIR=$(dirname $0)`
chore(build): split Dart and JS builds 2015-02-13 17:59:29 -05:00			`# this is needed because we're running JS tests in Dartium too`
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			`source $SCRIPT_DIR/env_dart.sh`
			`cd $SCRIPT_DIR/../..`

feat(build): enforce formatting of some files. Our style guide includes formatting conventions. Instead of wasting time in reviewing PRs discussing things like indenting, and to avoid later deltas to fix bad formatting in earlier commits, we want to enforce these in the build. The intent in this change is to fail the build as quickly as possible in travis, so those sending a PR immediately know they should run clang-format and update their commit. When running locally, we want users to know about formatting, but they may not want to act on it immediately, until they are done working. For this reason, it is only a warning outside of the continuous build. This is done by having a check-format task which should run on most local builds, and an enforce-format task only run by travis. 2015-04-11 16:29:32 -04:00			`./node_modules/.bin/gulp enforce-format build.js docs`