From 2db39170104e53194d0fd3e1fac6e22c047b6a7c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=B6ren=20Henning?= <soeren.henning@email.uni-kiel.de> Date: Fri, 3 Dec 2021 20:40:07 +0100 Subject: [PATCH] Fix missing link --- docs/running-benchmarks-old.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/running-benchmarks-old.md b/docs/running-benchmarks-old.md index 7c27860d1..9775c815f 100644 --- a/docs/running-benchmarks-old.md +++ b/docs/running-benchmarks-old.md @@ -26,7 +26,7 @@ The general process for running Theodolite benchmarks in operator mode is as fol Benchmarks are defined as resources of our custom resource definition `Benchmark`. You can either create a new `Benchmark` for your custom benchmark or system under test or deploy one of the existing benchmarks, which can be -found in [`theodolite-benchmarks/definitions`](theodolite-benchmarks/definitions). **TODO link** +found in [`theodolite-benchmarks/definitions`](https://github.com/cau-se/theodolite/tree/master/theodolite-benchmarks/definitions). Suppose your `Benchmark` resource is stored in `example-benchmark.yaml`, you can deploy it by running: -- GitLab