30c4454056
It looks like this needs to be set for the tvix pipeline to succeed. It was set to `canon` for `tvl-kit` (not sure if manually, or some autodetection previously did it for us that's not present anymore). Anyways, this sets it to how it's set in the web interface, to hopefully fix it. Change-Id: Ic3eb60e3f421fa949a84dcdaa928823ff45f679a Reviewed-on: https://cl.tvl.fyi/c/depot/+/8008 Reviewed-by: tazjin <tazjin@tvl.su> Tested-by: BuildkiteCI Autosubmit: flokli <flokli@flokli.de> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| default.nix | ||
| README.md | ||
| steps-depot.yml | ||
| steps-tvix.yml | ||
| steps-tvl-kit.yml | ||
| tvl.tf | ||
Buildkite configuration
This contains Terraform configuration for setting up our Buildkite pipelines.
Each pipeline (such as the one for depot itself, or exported subsets of the depot) needs some static configuration stored in Buildkite.
Through //tools/depot-deps a tf-buildkite binary is made available
which contains a Terraform binary pre-configured with the correct
providers. This is automatically on your $PATH through direnv.
However, secrets still need to be loaded to access the Terraform state
and speak to the Buildkite API. These are available to certain users
through //ops/secrets.
This can be done with separate direnv configuration, for example:
# //ops/buildkite/.envrc
source_up
eval $(age --decrypt -i ~/.ssh/id_ed25519 $(git rev-parse --show-toplevel)/ops/secrets/tf-buildkite.age)