b15a403c71
The `aio_monitoring_next` CircleCI job was disabled due to a failure in [302254](https://circleci.com/gh/angular/angular/302254). It turned out the failure was caused because the job happened to run after a change had been merged into master and right before it was deployed to https://next.angular.io/ causing the tests not to match the deployed version. This commit re-enables the job and moves it to a different time, when it is less likely that PRs will be being merged (and thus reducing the risk of a similar timming issue). Fixes #30101 PR Close #30168
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