d43187f7ef
In #35004, we started ignoring yarn's engines check for `yarn install` in AIO's `test-production.sh` script to fix a failure in the `aio_monitoring_stable` CI job. (See #35004 for details.) It turns out that the version of yarn used on the stable branch (1.17.3) `--ignore-engines` is needed on all yarn commands (including `yarn run`). Thus, #35004 is not enough to fix the failures. New example failure: https://circleci.com/gh/angular/angular/604341 This commit turns of the engines check for the whole `aio_monitoring_stable` CI job to fix the failure and make the job more robust. PR Close #35033
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