honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/aio/scripts/deploy-to-firebase.sh

44 lines
992 B
Bash
Raw Normal View History

ci(aio): deploy commits on the stable branch to production The current stable branch is determined based on the current version mapped to the npm `latest` tag (by replacing the patch version number with 'x' - e.g. `1.2.3` --> `1.2.x`). PRs against the stable branch will be deployed to the preview server (as long as the rest of the requirements are met). Commits on the stable branch itself will be deployed to production. Fixes #16908
2017-05-23 04:36:02 -04:00
#!/usr/bin/env bash
# WARNING: FIREBASE_TOKEN should NOT be printed.
set +x -eu -o pipefail
readonly deployEnv=$1
case $deployEnv in
staging)
build(aio): add staging environment You can now specify what environment you are building by add it to the `yarn build` command. For example: ``` yarn build -- --env=stage ``` Moreover the `deploy-to-firebase.sh` script will automatically apply the appropriate environment.
2017-06-12 18:51:39 -04:00
readonly buildEnv=stage
ci(aio): deploy commits on the stable branch to production The current stable branch is determined based on the current version mapped to the npm `latest` tag (by replacing the patch version number with 'x' - e.g. `1.2.3` --> `1.2.x`). PRs against the stable branch will be deployed to the preview server (as long as the rest of the requirements are met). Commits on the stable branch itself will be deployed to production. Fixes #16908
2017-05-23 04:36:02 -04:00
readonly projectId=aio-staging
readonly deployedUrl=https://$projectId.firebaseapp.com/
readonly firebaseToken=$FIREBASE_TOKEN
;;
production)
build(aio): add staging environment You can now specify what environment you are building by add it to the `yarn build` command. For example: ``` yarn build -- --env=stage ``` Moreover the `deploy-to-firebase.sh` script will automatically apply the appropriate environment.
2017-06-12 18:51:39 -04:00
readonly buildEnv=prod
ci(aio): deploy commits on the stable branch to production The current stable branch is determined based on the current version mapped to the npm `latest` tag (by replacing the patch version number with 'x' - e.g. `1.2.3` --> `1.2.x`). PRs against the stable branch will be deployed to the preview server (as long as the rest of the requirements are met). Commits on the stable branch itself will be deployed to production. Fixes #16908
2017-05-23 04:36:02 -04:00
readonly projectId=angular-io
readonly deployedUrl=https://angular.io/
readonly firebaseToken=$FIREBASE_TOKEN
;;
*)
echo "Unknown deployment environment ('$deployEnv'). Expected 'staging' or 'production'."
exit 1
;;
esac
(
cd "`dirname $0`/.."
# Build the app
build(aio): add staging environment You can now specify what environment you are building by add it to the `yarn build` command. For example: ``` yarn build -- --env=stage ``` Moreover the `deploy-to-firebase.sh` script will automatically apply the appropriate environment.
2017-06-12 18:51:39 -04:00
yarn build -- --env=$buildEnv
ci(aio): deploy commits on the stable branch to production The current stable branch is determined based on the current version mapped to the npm `latest` tag (by replacing the patch version number with 'x' - e.g. `1.2.3` --> `1.2.x`). PRs against the stable branch will be deployed to the preview server (as long as the rest of the requirements are met). Commits on the stable branch itself will be deployed to production. Fixes #16908
2017-05-23 04:36:02 -04:00
ci(aio): remove umd
2017-06-16 19:25:42 -04:00
# Check payload size
yarn payload-size
ci(aio): deploy commits on the stable branch to production The current stable branch is determined based on the current version mapped to the npm `latest` tag (by replacing the patch version number with 'x' - e.g. `1.2.3` --> `1.2.x`). PRs against the stable branch will be deployed to the preview server (as long as the rest of the requirements are met). Commits on the stable branch itself will be deployed to production. Fixes #16908
2017-05-23 04:36:02 -04:00
# Deploy to Firebase
firebase use "$projectId" --token "$firebaseToken"
firebase deploy --message "Commit: $TRAVIS_COMMIT" --non-interactive --token "$firebaseToken"
# Run PWA-score tests
ci(aio): avoid printing too large PWA report (and restore `print-logs.sh`) There have been some issues lately with Travis jobs failing due to `print-log.sh`. This is likely due to trying to print the Lighthouse PWA report, which is too large. This commit stops printing that report (since it was rarely used and is pretty easy to acquire when needed) and restores the `print-logs.sh` script (that was temporarily removed with dfcca66fd).
2017-06-30 05:09:53 -04:00
yarn test-pwa-score -- "$deployedUrl" "$MIN_PWA_SCORE"
ci(aio): deploy commits on the stable branch to production The current stable branch is determined based on the current version mapped to the npm `latest` tag (by replacing the patch version number with 'x' - e.g. `1.2.3` --> `1.2.x`). PRs against the stable branch will be deployed to the preview server (as long as the rest of the requirements are met). Commits on the stable branch itself will be deployed to production. Fixes #16908
2017-05-23 04:36:02 -04:00
)