iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/.circleci/env.sh

114 lines
6.9 KiB
Bash
Raw Normal View History

ci: move CircleCI env variables definition to shell script (#26596) PR Close #26596
2018-10-23 09:34:45 -04:00
#!/usr/bin/env bash
ci: compute commit range for rerun workflows (#27775) On push builds, CircleCI provides `CIRCLE_COMPARE_URL`, which we use to extract the commit range for a given build. When a workflow is rerun (e.g. to recover from a flaked job), `CIRCLE_COMPARE_URL` is not defined, causing some jobs to fail. This commit fixes it by retrieving the compare URL from the original workflow. It uses a slow process involving a (potentially large) number of requests to CircleCI API. It depends on the (undocumented) fact, that the `workspace_id` is the same on all rerun workflows and the same as the original `workflow_id`. PR Close #27775
2018-12-20 08:49:22 -05:00
# Variables
ci: combine "define_env_vars" and "download_yarn" anchor (#28788) As discussed in https://github.com/angular/angular/pull/28546#discussion_r254068014, we want to combine the `define_env_vars` and `download_yarn` anchor since downloading Yarn depends on setting up the environment variables. In addition this simplifies our setup and reduces code-duplication. PR Close #28788
2019-02-17 13:38:37 -05:00
readonly projectDir=$(realpath "$(dirname ${BASH_SOURCE[0]})/..")
readonly envHelpersPath="$projectDir/.circleci/env-helpers.inc.sh";
build: ensure that refs and shas for PRs only need to be requested once (#36207) This is done by requesting the refs and shas for the PR when the env.sh script is run. Additionally, the env.sh script is now setup to write all of the environment variables created to a cache file and subsequent loads of the environment load the values from there. The get-refs-and-shas-for-target.js script now also first attempts to load the refs and shas from an environment variable before falling back to requesting from github via the API. PR Close #36207
2020-03-23 14:22:57 -04:00
readonly bashEnvCachePath="$projectDir/.circleci/bash_env_cache";
ci: compute commit range for rerun workflows (#27775) On push builds, CircleCI provides `CIRCLE_COMPARE_URL`, which we use to extract the commit range for a given build. When a workflow is rerun (e.g. to recover from a flaked job), `CIRCLE_COMPARE_URL` is not defined, causing some jobs to fail. This commit fixes it by retrieving the compare URL from the original workflow. It uses a slow process involving a (potentially large) number of requests to CircleCI API. It depends on the (undocumented) fact, that the `workspace_id` is the same on all rerun workflows and the same as the original `workflow_id`. PR Close #27775
2018-12-20 08:49:22 -05:00
ci: removing CI environment variable caching setup (#36936) A caching mechanism was put in place to prevent repeated calls to the Github API. As the CI setup no longer relies on calls to the Github API, this caching is no longer necessary. It was discovered that this caching was causing a contention issue for saucelabs testing as the same tunnel was being reused for multiple jobs simultaneously. With this caching mechanism removed the jobs will once again run via separate tunnels. PR Close #36936
2020-05-05 11:55:55 -04:00
# Load helpers and make them available everywhere (through `$BASH_ENV`).
source $envHelpersPath;
echo "source $envHelpersPath;" >> $BASH_ENV;
ci: move CircleCI env variables definition to shell script (#26596) PR Close #26596
2018-10-23 09:34:45 -04:00
ci(docs-infra): use the tests from the stable branch in `aio_monitoring_stable` CircleCI job (#30110) Previously, the `aio_monitoring_stable` job (which runs tests against https://angular.io/) was using the tests from the master branch. As a result, if the master branch included changes in those tests that were not yet backported to the stable branch (and thus deployed to https://angular.io/), the tests would fail. This commit fixes this by using the tests from the stable branch to test against https://angular.io/. Fixes #30101 PR Close #30110
2019-04-25 06:59:16 -04:00
ci: removing CI environment variable caching setup (#36936) A caching mechanism was put in place to prevent repeated calls to the Github API. As the CI setup no longer relies on calls to the Github API, this caching is no longer necessary. It was discovered that this caching was causing a contention issue for saucelabs testing as the same tunnel was being reused for multiple jobs simultaneously. With this caching mechanism removed the jobs will once again run via separate tunnels. PR Close #36936
2020-05-05 11:55:55 -04:00
####################################################################################################
# Define PUBLIC environment variables for CircleCI.
####################################################################################################
# See https://circleci.com/docs/2.0/env-vars/#built-in-environment-variables for more info.
####################################################################################################
setPublicVar CI "$CI"
setPublicVar PROJECT_ROOT "$projectDir";
setPublicVar CI_AIO_MIN_PWA_SCORE "95";
# This is the branch being built; e.g. `pull/12345` for PR builds.
setPublicVar CI_BRANCH "$CIRCLE_BRANCH";
setPublicVar CI_BUILD_URL "$CIRCLE_BUILD_URL";
setPublicVar CI_COMMIT "$CIRCLE_SHA1";
# `CI_COMMIT_RANGE` is only used on push builds (a.k.a. non-PR, non-scheduled builds and rerun
# workflows of such builds).
setPublicVar CI_GIT_BASE_REVISION "${CIRCLE_GIT_BASE_REVISION}";
setPublicVar CI_GIT_REVISION "${CIRCLE_GIT_REVISION}";
setPublicVar CI_COMMIT_RANGE "$CIRCLE_GIT_BASE_REVISION..$CIRCLE_GIT_REVISION";
setPublicVar CI_PULL_REQUEST "${CIRCLE_PR_NUMBER:-false}";
setPublicVar CI_REPO_NAME "$CIRCLE_PROJECT_REPONAME";
setPublicVar CI_REPO_OWNER "$CIRCLE_PROJECT_USERNAME";
setPublicVar CI_PR_REPONAME "$CIRCLE_PR_REPONAME";
setPublicVar CI_PR_USERNAME "$CIRCLE_PR_USERNAME";
ci(docs-infra): use the tests from the stable branch in `aio_monitoring_stable` CircleCI job (#30110) Previously, the `aio_monitoring_stable` job (which runs tests against https://angular.io/) was using the tests from the master branch. As a result, if the master branch included changes in those tests that were not yet backported to the stable branch (and thus deployed to https://angular.io/), the tests would fail. This commit fixes this by using the tests from the stable branch to test against https://angular.io/. Fixes #30101 PR Close #30110
2019-04-25 06:59:16 -04:00
ci: move CircleCI env variables definition to shell script (#26596) PR Close #26596
2018-10-23 09:34:45 -04:00
ci: removing CI environment variable caching setup (#36936) A caching mechanism was put in place to prevent repeated calls to the Github API. As the CI setup no longer relies on calls to the Github API, this caching is no longer necessary. It was discovered that this caching was causing a contention issue for saucelabs testing as the same tunnel was being reused for multiple jobs simultaneously. With this caching mechanism removed the jobs will once again run via separate tunnels. PR Close #36936
2020-05-05 11:55:55 -04:00
####################################################################################################
# Define "lazy" PUBLIC environment variables for CircleCI.
# (I.e. functions to set an environment variable when called.)
####################################################################################################
createPublicVarSetter CI_STABLE_BRANCH "\$(npm info @angular/core dist-tags.latest | sed -r 's/^\\s*([0-9]+\\.[0-9]+)\\.[0-9]+.*$/\\1.x/')";
ci: move CircleCI env variables definition to shell script (#26596) PR Close #26596
2018-10-23 09:34:45 -04:00
ci: move local and saucelabs unit tests to circle (#27937) Moving the tests over to CircleCI in pretty much "as-is" state just so that we can drop the dependency on Travis. In the followup changes we plan to migrate these tests to run on sauce under bazel. @gregmagolan is working on that. I've previously verified that all the tests executed in legacy-unit-tests-local already under bazel. Therefore the legacy-unit-tests-local job is strictly not necessary any more, but given how flaky legacy-unit-tests-saucelabs is, it is good to have the -local job just so that we can quickly determine if any failure is a flake or legit issue (the bazel version of these tests could theoretically run in a slightly different way and fail or not fail in a different way, so having -lcoal job is just an extra safety check). This change was coauthored with @devversion PR Close #27937
2019-01-04 14:58:33 -05:00
ci: removing CI environment variable caching setup (#36936) A caching mechanism was put in place to prevent repeated calls to the Github API. As the CI setup no longer relies on calls to the Github API, this caching is no longer necessary. It was discovered that this caching was causing a contention issue for saucelabs testing as the same tunnel was being reused for multiple jobs simultaneously. With this caching mechanism removed the jobs will once again run via separate tunnels. PR Close #36936
2020-05-05 11:55:55 -04:00
####################################################################################################
# Define SECRET environment variables for CircleCI.
####################################################################################################
setSecretVar CI_SECRET_AIO_DEPLOY_FIREBASE_TOKEN "$AIO_DEPLOY_TOKEN";
setSecretVar CI_SECRET_PAYLOAD_FIREBASE_TOKEN "$ANGULAR_PAYLOAD_TOKEN";
ci: ensure saucelabs browsers can load karma test page (#35171) In the past we had connecitivity issues on Saucelabs. Browsers on mobile devices were not able to properly resolve the `localhost` hostname through the tunnel. This is because the device resolves `localhost` or `127.0.0.1` to the actual Saucelabs device, while it should resolve to the tunnel host machine (in our case the CircleCI VM). In the past, we simply disabled the failing devices and re-enabled the devices later. At this point, the Saucelabs team claimed that the connecitivy/proxy issues were fixed. Saucelabs seems to have a process for VMs which ensures that requests to `localhost` / `127.0.0.1` are properly resolved through the tunnel. This process is not very reliable and can cause tests to fail. Related issues have been observed/mentioned in the Saucelabs support docs. e.g. https://support.saucelabs.com/hc/en-us/articles/115002212447-Unable-to-Reach-Application-on-localhost-for-Tests-Run-on-Safari-8-and-9-and-Edge https://support.saucelabs.com/hc/en-us/articles/225106887-Safari-and-Internet-Explorer-Won-t-Load-Website-When-Using-Sauce-Connect-on-Localhost In order to ensure that requests are always resolved through the tunnel, we add our own domain alias in the CircleCI's hosts file, and enforce that it is always resolved through the tunnel (using the `--tunnel-domains` SC flag). Saucelabs devices by default will never resolve this domain/hostname to the actual local Saucelabs device. PR Close #35171
2020-02-06 08:17:03 -05:00
build: ensure that refs and shas for PRs only need to be requested once (#36207) This is done by requesting the refs and shas for the PR when the env.sh script is run. Additionally, the env.sh script is now setup to write all of the environment variables created to a cache file and subsequent loads of the environment load the values from there. The get-refs-and-shas-for-target.js script now also first attempts to load the refs and shas from an environment variable before falling back to requesting from github via the API. PR Close #36207
2020-03-23 14:22:57 -04:00
ci: removing CI environment variable caching setup (#36936) A caching mechanism was put in place to prevent repeated calls to the Github API. As the CI setup no longer relies on calls to the Github API, this caching is no longer necessary. It was discovered that this caching was causing a contention issue for saucelabs testing as the same tunnel was being reused for multiple jobs simultaneously. With this caching mechanism removed the jobs will once again run via separate tunnels. PR Close #36936
2020-05-05 11:55:55 -04:00
####################################################################################################
# Define SauceLabs environment variables for CircleCI.
####################################################################################################
setPublicVar SAUCE_USERNAME "angular-framework";
setSecretVar SAUCE_ACCESS_KEY "0c731274ed5f-cbc9-16f4-021a-9835e39f";
# TODO(josephperrott): Remove environment variables once all saucelabs tests are via bazel method.
setPublicVar SAUCE_LOG_FILE /tmp/angular/sauce-connect.log
setPublicVar SAUCE_READY_FILE /tmp/angular/sauce-connect-ready-file.lock
setPublicVar SAUCE_PID_FILE /tmp/angular/sauce-connect-pid-file.lock
setPublicVar SAUCE_TUNNEL_IDENTIFIER "angular-framework-${CIRCLE_BUILD_NUM}-${CIRCLE_NODE_INDEX}"
# Amount of seconds we wait for sauceconnect to establish a tunnel instance. In order to not
# acquire CircleCI instances for too long if sauceconnect failed, we need a connect timeout.
setPublicVar SAUCE_READY_FILE_TIMEOUT 120
build: ensure that refs and shas for PRs only need to be requested once (#36207) This is done by requesting the refs and shas for the PR when the env.sh script is run. Additionally, the env.sh script is now setup to write all of the environment variables created to a cache file and subsequent loads of the environment load the values from there. The get-refs-and-shas-for-target.js script now also first attempts to load the refs and shas from an environment variable before falling back to requesting from github via the API. PR Close #36207
2020-03-23 14:22:57 -04:00
ci: remove reliance on Github API for CI setup (#36500) Previously our CI during the setup process has made requests to the Github API to determine the target branch and shas. With this change, this information is now determined via git commands using pipeline parameters from CircleCI. PR Close #36500
2020-04-08 00:10:04 -04:00
ci: removing CI environment variable caching setup (#36936) A caching mechanism was put in place to prevent repeated calls to the Github API. As the CI setup no longer relies on calls to the Github API, this caching is no longer necessary. It was discovered that this caching was causing a contention issue for saucelabs testing as the same tunnel was being reused for multiple jobs simultaneously. With this caching mechanism removed the jobs will once again run via separate tunnels. PR Close #36936
2020-05-05 11:55:55 -04:00
####################################################################################################
# Define environment variables for the `angular/components` repo unit tests job.
####################################################################################################
# We specifically use a directory within "/tmp" here because we want the cloned repo to be
# completely isolated from angular/angular in order to avoid any bad interactions between
# their separate build setups. **NOTE**: When updating the temporary directory, also update
# the `save_cache` path configuration in `config.yml`
setPublicVar COMPONENTS_REPO_TMP_DIR "/tmp/angular-components-repo"
setPublicVar COMPONENTS_REPO_URL "https://github.com/angular/components.git"
setPublicVar COMPONENTS_REPO_BRANCH "master"
# **NOTE**: When updating the commit SHA, also update the cache key in the CircleCI `config.yml`.
test: update components repo to test against recent revision (#38273) The changes in angular/components#20136 are required to allow the framework tests to succeed. PR Close #38273
2020-07-29 17:44:03 -04:00
setPublicVar COMPONENTS_REPO_COMMIT "09e68db8ed5b1253f2fe38ff954ef0df019fc25a"
ci: move local and saucelabs unit tests to circle (#27937) Moving the tests over to CircleCI in pretty much "as-is" state just so that we can drop the dependency on Travis. In the followup changes we plan to migrate these tests to run on sauce under bazel. @gregmagolan is working on that. I've previously verified that all the tests executed in legacy-unit-tests-local already under bazel. Therefore the legacy-unit-tests-local job is strictly not necessary any more, but given how flaky legacy-unit-tests-saucelabs is, it is good to have the -local job just so that we can quickly determine if any failure is a flake or legit issue (the bazel version of these tests could theoretically run in a slightly different way and fail or not fail in a different way, so having -lcoal job is just an extra safety check). This change was coauthored with @devversion PR Close #27937
2019-01-04 14:58:33 -05:00
ci: move setup of bazel configurations into the env init scripts (#34834) Since we always set up bazel on both our windows and linux CI runs, we should consider this configuration part of the environment setup. PR Close #34834
2020-01-17 12:06:48 -05:00
####################################################################################################
# Decrypt GCP Credentials and store them as the Google default credentials.
####################################################################################################
mkdir -p "$HOME/.config/gcloud";
openssl aes-256-cbc -d -in "${projectDir}/.circleci/gcp_token" \
-md md5 -k "$CIRCLE_PROJECT_REPONAME" -out "$HOME/.config/gcloud/application_default_credentials.json"
####################################################################################################
# Set bazel configuration for CircleCI runs.
####################################################################################################
cp "${projectDir}/.circleci/bazel.linux.rc" "$HOME/.bazelrc";
build: remove legacy integration test runner (#35985) * integration tests target definitions in integration/BUILD.bazel updated to use a single dict * payload tracking for integration tests updated to work under Bazel * legacy integration_test CI job removed * integration/run_tests.sh script no longer used in CI so it has been updated for running integration tests locally in the legacy way PR Close #35985
2020-03-10 01:17:48 -04:00
####################################################################################################
# Create shell script in /tmp for Bazel actions to access CI envs without
# busting the cache. Used by payload-size.sh script in integration tests.
####################################################################################################
readonly bazelVarEnv="/tmp/bazel-ci-env.sh"
echo "# Setup by /.circle/env.sh" > $bazelVarEnv
echo "export PROJECT_ROOT=\"${PROJECT_ROOT}\";" >> $bazelVarEnv
echo "export CI_BRANCH=\"${CI_BRANCH}\";" >> $bazelVarEnv
echo "export CI_BUILD_URL=\"${CI_BUILD_URL}\";" >> $bazelVarEnv
echo "export CI_COMMIT=\"${CI_COMMIT}\";" >> $bazelVarEnv
echo "export CI_COMMIT_RANGE=\"${CI_COMMIT_RANGE}\";" >> $bazelVarEnv
echo "export CI_PULL_REQUEST=\"${CI_PULL_REQUEST}\";" >> $bazelVarEnv
echo "export CI_REPO_NAME=\"${CI_REPO_NAME}\";" >> $bazelVarEnv
echo "export CI_REPO_OWNER=\"${CI_REPO_OWNER}\";" >> $bazelVarEnv
echo "export CI_SECRET_PAYLOAD_FIREBASE_TOKEN=\"${CI_SECRET_PAYLOAD_FIREBASE_TOKEN}\";" >> $bazelVarEnv
ci: move setup of bazel configurations into the env init scripts (#34834) Since we always set up bazel on both our windows and linux CI runs, we should consider this configuration part of the environment setup. PR Close #34834
2020-01-17 12:06:48 -05:00
####################################################################################################
####################################################################################################
## Source `$BASH_ENV` to make the variables available immediately. ##
## ***NOTE: This must remain the the last action in this script*** ##
####################################################################################################
####################################################################################################
ci: move CircleCI env variables definition to shell script (#26596) PR Close #26596
2018-10-23 09:34:45 -04:00
source $BASH_ENV;