History

Paul Gschwendtner 69265b7b5d ci(docs-infra): "test_aio_local_ivy" job should attach ivy package output (#29117 )

Currently the "test_docs_examples_ivy" job attaches
the legacy package output, while we can also attach
the Ivy NPM package output. We don't need Ngcc to downlevel
the Angular packages in order to build AIO with Ivy.

PR Close #29117

2019-03-05 11:41:44 -08:00

bazel.rc

build: fix bazel repositories not cached on circleci (#28515 )

2019-02-05 13:06:24 -05:00

config.yml

ci(docs-infra): "test_aio_local_ivy" job should attach ivy package output (#29117 )

2019-03-05 11:41:44 -08:00

env-helpers.inc.sh

ci: fix setting env var with spaces in value (#28494 )

2019-02-01 20:22:03 -05:00

env.sh

ci: print sauce-connect log output on timeout (#29084 )

2019-03-04 10:10:28 -08:00

gcp_token

build(bazel): Run build-packages-dist on RBE (#25237 )

2018-08-20 16:34:45 -07:00

get-commit-range.js

docs: document why not using compare-url orb (#28010 )

2019-01-10 10:50:30 -08:00

github_token

ci: re-encrypt .circleci/github_token (#26698 )

2018-10-23 13:31:48 -07:00

README.md

build: use bazel version from node modules (#26691 )

2018-10-30 16:19:13 -04:00

setup_cache.sh

Revert "build: update to newer circleCI bazel remote cache proxy (#25054 )" (#25076 )

2018-07-24 16:05:58 -07:00

trigger-webhook.js

ci(docs-infra): manually trigger the preview server webhook (#27458 )

2018-12-04 13:59:54 -08:00

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