f8741c0985
By splitting the jobs, if something goes wrong with deploying (e.g. a network issue), we can re-run just that part instead of having to wait for all the tests to complete again. In terms of total duration, the difference should be minimal, because the two operations (testing and deploying) do not depend on shared tasks. For example, we need to build again (for the specific target environment; e.g. stable, next, etc.) before deploying anyway. PR Close #26746 |
||
|---|---|---|
| .. | ||
| README.md | ||
| bazel.rc | ||
| config.yml | ||
| gcp_token | ||
| github_token | ||
| rbe-bazel.rc | ||
| setup_cache.sh | ||
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 ngcontainer docker image so you use the same version of openssl as we will at runtime:
docker run --rm -it angular/ngcontainer - 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