feat(ops/pipelines): Add Buildkite pipeline configuration r/1099

This adds configuration which generates the structure expected for
Buildkite pipelines, which can then be dynamically ingested by
Buildkite when a pipeline is triggered.

Change-Id: I61e3dc3affb19c1f2550ef827fa73b17f8d8ae47
Reviewed-on: https://cl.tvl.fyi/c/depot/+/627
Reviewed-by: ericvolp12 <ericvolp12@gmail.com>
Reviewed-by: lukegb <lukegb@tvl.fyi>

1 files changed, 21 insertions, 0 deletions

diff --git a/ops/pipelines/depot.nix b/ops/pipelines/depot.nix
new file mode 100644
index 000000000000..40de18b5de36
--- /dev/null
+++ b/ops/pipelines/depot.nix
@@ -0,0 +1,21 @@
+# This file configures the primary build pipeline used for the
+# top-level list of depot targets.
+#
+# It outputs a "YAML" (actually JSON) file which is evaluated and
+# submitted to Buildkite at the start of each build. This means we can
+# dynamically configure the pipeline execution here.
+{ depot, pkgs, ... }:
+
+let
+  inherit (builtins) toJSON;
+  inherit (pkgs) writeText;
+
+  # This defines the build pipeline, using the pipeline format
+  # documented on https://buildkite.com/docs/pipelines/defining-steps
+  pipeline.steps = [
+    {
+      command = "nix-build -A ciBuilds.__allTargets";
+      label = "all-targets";
+    }
+  ];
+in writeText "depot.yaml" (toJSON pipeline)