daml/infra
Jonas Chevalier 16aba583ce
CI linux agent changes (#509)
* ci: always use the linux-pool

reduce the difference of environment between external and internal
contributions

* infra: tweak the linux cache warmup script

Don't share the same bazel cache directory with the disk cache, which is
something else. Be more specific about the target. Clean after yourself.

* infra: bump the linux agent disk to 200GB

avoid running out of disk space
2019-04-16 11:35:46 +02:00
..
modules/gcp_cdn_bucket open-sourcing daml 2019-04-04 09:33:38 +01:00
.gitignore open-sourcing daml 2019-04-04 09:33:38 +01:00
apply open-sourcing daml 2019-04-04 09:33:38 +01:00
bazel_cache.tf open-sourcing daml 2019-04-04 09:33:38 +01:00
main.tf add more Azure Pipeline agents (#230) 2019-04-09 18:59:37 +02:00
nix_cache.tf add more Azure Pipeline agents (#230) 2019-04-09 18:59:37 +02:00
README.md open-sourcing daml 2019-04-04 09:33:38 +01:00
vsts_agent_linux_startup.sh CI linux agent changes (#509) 2019-04-16 11:35:46 +02:00
vsts_agent_linux.tf CI linux agent changes (#509) 2019-04-16 11:35:46 +02:00
writer.tf open-sourcing daml 2019-04-04 09:33:38 +01:00

DAML

This is the terraform code used by the DAML repository to deploy supporting infrastructure such as the Bazel and Nix caches.

Setup

To deploy the infrastructure changes, you will to get access to the da-dev-gcp-daml-language Google project from IT. Then run gcloud auth login to configure the local credentials.

Deployment

All the infrastructure is currently deployed using Terraform. For convenience we have a little wrapper script that you can run to apply the latest changes:

$ ./apply

Writer service-account key

To avoid holding the secret key into the store, creating the key has to be done through the UI.

This can be done here: https://console.cloud.google.com/iam-admin/serviceaccounts/details/104272946446260011088?project=da-dev-gcp-daml-language