teleport/.cloudbuild/ci
Trent Clarke cce6db2e5f
Google CloudBuild support (#9090)
Part of this change is implementing a "no secrets" policy for CI. Given that

    we have to support CI for arbitrary external contributors, and
    it is easy to craft a malicious PR that exfiltrates secrets during a CI build

any test that runs under CI must be able to do so without any injected secrets.

This means that several of the test we currently run under Drone will not be run on GCB, at least as part of the regular CI. The plan is to create a separate task that periodically runs tests that require external credentials (e.g. Kube tests, various backend data stores, etc.) in a more secure way and report failures asynchronously. And while these tests will not run under CI, the should still be built under CI so that required changes are caught during review.
2021-11-30 12:12:16 +11:00
..
doc-tests.yaml Google CloudBuild support (#9090) 2021-11-30 12:12:16 +11:00
integration-tests.yaml Google CloudBuild support (#9090) 2021-11-30 12:12:16 +11:00
lint.yaml Google CloudBuild support (#9090) 2021-11-30 12:12:16 +11:00
unit-tests.yaml Google CloudBuild support (#9090) 2021-11-30 12:12:16 +11:00