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

41 lines
967 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
# Deploy to Firebase
firebase use "$projectId" --token "$firebaseToken"
firebase deploy --message "Commit: $TRAVIS_COMMIT" --non-interactive --token "$firebaseToken"
# Run PWA-score tests
ci(aio): fail the build if the PWA score is too low Previously, there was an issue with testing the PWA score on staging and failing the build was temporarily disabled. It works now, so we need to enable failing the build is the score drops below some threshold.
2017-06-12 19:23:11 -04:00
yarn test-pwa-score -- "$deployedUrl" "$MIN_PWA_SCORE" "$PWA_RESULTS_LOG"
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
)