angular.js/scripts/travis/build.sh

#!/bin/bash

set -e

export SAUCE_ACCESS_KEY=`echo $SAUCE_ACCESS_KEY | rev`

if [ $JOB = "unit" ]; then
  grunt ci-checks
  grunt test:docgen
  grunt test:promises-aplus
  grunt test:unit --browsers SL_Chrome,SL_Safari,SL_Firefox,SL_IE_8,SL_IE_9,SL_IE_10,SL_IE_11 --reporters dots
elif [ $JOB = "e2e" ]; then
  grunt test:protractor --sauceUser $SAUCE_USERNAME \
      --sauceKey $SAUCE_ACCESS_KEY \
      --capabilities.tunnel-identifier=$TRAVIS_JOB_NUMBER \
      --capabilities.build=$TRAVIS_BUILD_NUMBER
else
  echo "Unknown job type. Please set JOB=unit or JOB=e2e."
fi
chore(bower): write grunt task for running bower 2013-07-30 22:25:54 +00:00			`#!/bin/bash`

chore(travis): clean up the build output 2013-08-28 19:09:13 +00:00			`set -e`
chore(bower): write grunt task for running bower 2013-07-30 22:25:54 +00:00
			export SAUCE_ACCESS_KEY=`echo $SAUCE_ACCESS_KEY \| rev`
chore: run more browsers on Travis (IE8,IE9,IE10,Safari,FF) Also instead of running everything in parallel, there are only two parallel tasks: - e2e tests running in the background (only on Chrome) - all the unit tests running sequentially 2013-08-20 21:43:15 +00:00
chore(travis): run two jobs Instead of parallelization on a single Travis VM, we use two VMs. - output is nicer (we don't have to buffer e2e tests and then show it at the end) - you can easily see faster the result of unit tests (as it's basically a separate build) We should also make sure we only do the necesary stuff (for install we don't need to do `grunt package` for unit tests, we only need to generate the docs for e2e tests. 2013-12-11 09:02:56 +00:00			`if [ $JOB = "unit" ]; then`
			`grunt ci-checks`
			`grunt test:docgen`
			`grunt test:promises-aplus`
			`grunt test:unit --browsers SL_Chrome,SL_Safari,SL_Firefox,SL_IE_8,SL_IE_9,SL_IE_10,SL_IE_11 --reporters dots`
			`elif [ $JOB = "e2e" ]; then`
feat(build): add a grunt test for running protractor tests extracted from the docs 2014-01-07 19:51:32 +00:00			`grunt test:protractor --sauceUser $SAUCE_USERNAME \`
			`--sauceKey $SAUCE_ACCESS_KEY \`
			`--capabilities.tunnel-identifier=$TRAVIS_JOB_NUMBER \`
			`--capabilities.build=$TRAVIS_BUILD_NUMBER`
chore(travis): run two jobs Instead of parallelization on a single Travis VM, we use two VMs. - output is nicer (we don't have to buffer e2e tests and then show it at the end) - you can easily see faster the result of unit tests (as it's basically a separate build) We should also make sure we only do the necesary stuff (for install we don't need to do `grunt package` for unit tests, we only need to generate the docs for e2e tests. 2013-12-11 09:02:56 +00:00			`else`
			`echo "Unknown job type. Please set JOB=unit or JOB=e2e."`
			`fi`