honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/aio/aio-builds-setup/scripts/travis-preverify-pr.sh

27 lines
712 B
Bash
Raw Normal View History

ci(aio): do not deploy PR if preconditions not met This avoids incorrectly failing the build if the PR author is not a member of one of the whitelisted GitHub teams.
2017-03-07 04:39:37 -05:00
#!/bin/bash
set -eux -o pipefail
# Set up env
refactor(aio): drop `run` (from `yarn run`), rename script and remove unnecessary cmds
2017-05-12 04:15:08 -04:00
source "`dirname $0`/_env.sh"
ci(aio): do not deploy PR if preconditions not met This avoids incorrectly failing the build if the PR author is not a member of one of the whitelisted GitHub teams.
2017-03-07 04:39:37 -05:00
ci(aio): build `aio-builds-setup` scripts before pre-verifying PR (Coincidentally), this wasn't an issue before fdfeaaf1f, because pre-verification was run after `test.sh`, during which `aio-builds-setup` was built. Now that `deploy-staging.sh` is being run before `test.sh`, we need to build the `aio-builds-setup` scripts first.
2017-05-12 04:08:45 -04:00
# Build `scripts-js/`
build: use subshells when changing directories This prevents being left in the wrong directory in case of error.
2017-05-12 15:07:51 -04:00
(
cd "$SCRIPTS_JS_DIR"
yarn install
yarn build
)
ci(aio): build `aio-builds-setup` scripts before pre-verifying PR (Coincidentally), this wasn't an issue before fdfeaaf1f, because pre-verification was run after `test.sh`, during which `aio-builds-setup` was built. Now that `deploy-staging.sh` is being run before `test.sh`, we need to build the `aio-builds-setup` scripts first.
2017-05-12 04:08:45 -04:00
ci(aio): do not deploy PR if preconditions not met This avoids incorrectly failing the build if the PR author is not a member of one of the whitelisted GitHub teams.
2017-03-07 04:39:37 -05:00
# Preverify PR
AIO_GITHUB_ORGANIZATION="angular" \
ci(aio): whitelist 'aio-contributors' for deploying PR previews
2017-03-13 14:34:53 -04:00
AIO_GITHUB_TEAM_SLUGS="angular-core,aio-contributors" \
ci(aio): do not deploy PR if preconditions not met This avoids incorrectly failing the build if the PR author is not a member of one of the whitelisted GitHub teams.
2017-03-07 04:39:37 -05:00
AIO_GITHUB_TOKEN=$(echo ${GITHUB_TEAM_MEMBERSHIP_CHECK_KEY} | rev) \
AIO_REPO_SLUG=$TRAVIS_REPO_SLUG \
feat(aio): enable previews for any PR This commit introduces the ability to show previews for PRs by any author. It works as follows: - The build artifacts of all PRs are uploaded to the preview server. - Automatically verified PRs (i.e. from trusted authors or having a specific label) are deployed and publicly accessible as usual. - PRs that could not be automatically verified are stored for later use (after re-verification). - A PR can be marked as "trusted" and make its preview publicly accessible by adding the GitHub label specified in the `AIO_TRUSTED_PR_LABEL` env var of the preview server. At the moment, there is no automatic mechanism for notifying the preview server about changes to the PR's verification status. The PR's "visibility" will be checked and updated every time a new build is uploaded.
2017-06-18 18:15:07 -04:00
AIO_TRUSTED_PR_LABEL="aio: preview" \
ci(aio): do not deploy PR if preconditions not met This avoids incorrectly failing the build if the PR author is not a member of one of the whitelisted GitHub teams.
2017-03-07 04:39:37 -05:00
AIO_PREVERIFY_PR=$TRAVIS_PULL_REQUEST \
node "$SCRIPTS_JS_DIR/dist/lib/upload-server/index-preverify-pr"
feat(aio): enable previews for any PR This commit introduces the ability to show previews for PRs by any author. It works as follows: - The build artifacts of all PRs are uploaded to the preview server. - Automatically verified PRs (i.e. from trusted authors or having a specific label) are deployed and publicly accessible as usual. - PRs that could not be automatically verified are stored for later use (after re-verification). - A PR can be marked as "trusted" and make its preview publicly accessible by adding the GitHub label specified in the `AIO_TRUSTED_PR_LABEL` env var of the preview server. At the moment, there is no automatic mechanism for notifying the preview server about changes to the PR's verification status. The PR's "visibility" will be checked and updated every time a new build is uploaded.
2017-06-18 18:15:07 -04:00
# Exit codes:
# - 0: The PR can be automatically trusted (i.e. author belongs to trusted team or PR has the "trusted PR" label).
# - 1: An error occurred.
# - 2: The PR cannot be automatically trusted.