Skip to content
Snippets Groups Projects
Commit 2db39170 authored by Sören Henning's avatar Sören Henning
Browse files

Fix missing link

parent 9906f5b3
No related branches found
No related tags found
1 merge request!164Add Theodolite docs
Pipeline #5417 passed
Stage: build
    Stage: test
      Stage: check
        Hide whitespace changes
        Inline Side-by-side
        docs/running-benchmarks-old.md
        + 1
        − 1
        View file @ 2db39170
        ...@@ -26,7 +26,7 @@ The general process for running Theodolite benchmarks in operator mode is as fol ...@@ -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 Benchmarks are defined as resources of our custom resource definition
        `Benchmark`. You can either create a new `Benchmark` for your custom benchmark `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 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 Suppose your `Benchmark` resource is stored in `example-benchmark.yaml`, you
        can deploy it by running: can deploy it by running:
        ......
        0% or .
        You are about to add 0 people to the discussion. Proceed with caution.
        Finish editing this message first!
        Please register or to comment