3e08347d8a
The docs examples tests are run both with Ivy turned off and on. When Ivy is turned on, ngcc is used to convert all dependencies (including the Angular framework packages to Ivy). Previously, in order to speed things up, the `test_docs_examples_ivy` CI job would use Angular packages built with Ivy (from `dist/packages-dist-ivy-aot`). This however was a deviation from what happens in real-world applications. This commit changes the `test_docs_examples_ivy` CI job to always use the regular Angular packages (as published on npm) and use ngcc to convert them to Ivy. Relevant discussion: https://github.com/angular/angular/pull/35091#discussion_r373775396 PR Close #36015 |
||
|---|---|---|
| .. | ||
| README.md | ||
| bazel.common.rc | ||
| bazel.linux.rc | ||
| bazel.windows.rc | ||
| config.yml | ||
| env-helpers.inc.sh | ||
| env.sh | ||
| gcp_token | ||
| github_token | ||
| setup_cache.sh | ||
| trigger-webhook.js | ||
| windows-env.ps1 | ||
README.md
Encryption
Based on https://github.com/circleci/encrypted-files
In the CircleCI web UI, we have a secret variable called KEY
https://circleci.com/gh/angular/angular/edit#env-vars
which is only exposed to non-fork builds
(see "Pass secrets to builds from forked pull requests" under
https://circleci.com/gh/angular/angular/edit#advanced-settings)
We use this as a symmetric AES encryption key to encrypt tokens like a GitHub token that enables publishing snapshots.
To create the github_token file, we take this approach:
- Find the angular-builds:token in http://valentine
- Go inside the CircleCI default docker image so you use the same version of openssl as we will at runtime:
docker run --rm -it circleci/node:10.12 - echo "https://[token]:@github.com" > credentials
- openssl aes-256-cbc -e -in credentials -out .circleci/github_token -k $KEY
- If needed, base64-encode the result so you can copy-paste it out of docker:
base64 github_token