a1ff0a4 test: use new scenario steps in all scenarios — radicle-ci-broker

Radicle CI broker

test: use new scenario steps in all scenarios

Lars Wirzenius committed 1 year ago

commit a1ff0a41b72dcfd261f626d4349331eac384127d
parent 964d3e1ed224a1efd21da67091e178984df2c53e

1 file changed +112 -207

modified ci-broker.md

@@ -223,8 +223,7 @@ output is in the JSON format. It does not try to make sure the JSON

 matches the YAML semantically.
 ~~~scenario
 given an installed CI broker
 given file broker.yaml
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 when I run cib --config broker.yaml config --output actual.json
 when I run jq . actual.json
 then command is successful

@@ -274,10 +273,7 @@ reports.

 _Who:_ `cib-devs`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 when I run cib --version
 then stdout matches regex ^radicle-ci-broker \d+\.\d+\.\d+$

@@ -303,23 +299,12 @@ user can access individual logs.

 _Who:_ `cib-devs`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given file refsfetched.json
 given file set-rid
 when I run bash radenv.sh env HOME=../homedir python3 set-rid refsfetched.json testy
 when I run synthetic-events synt.sock refsfetched.json --log log.txt
 given file adapter.sh from adapter-with-url.sh
 when I run chmod +x adapter.sh
 given file broker.yaml
 given a directory reports
 given a Radicle node, with CI configured with broker.yaml and adapter adapter-with-url.sh
 given a Git repository xyzzy in the Radicle node
 given the Radicle node emits a refsUpdated event for xyzzy
 when I try to run bash radenv.sh RAD_SOCKET=synt.sock cib --config broker.yaml insert
 when I run ./env.sh synthetic-events synt.sock event.json --log log.txt
 when I try to run ./env.sh cib --config broker.yaml insert
 then command is successful
 ~~~

@@ -342,15 +327,10 @@ reduces the support burden on the Radicle project.

 _Who:_ `cib-devs`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given file broker.yaml
 when I try to run bash radenv.sh RAD_SOCKET=xyzzy.sock cib --config broker.yaml insert
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 when I try to run ./env.sh cib --config broker.yaml insert
 then command fails
 then stderr contains "node control socket does not exist: xyzzy.sock"
 then stderr contains "node control socket does not exist: synt.sock"
 ~~~

@@ -370,14 +350,8 @@ a thing that can always be made better. We can later add more

 scenarios if we tighten the acceptance criteria.
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given file broker.yaml
 given file not-yaml.yaml
 when I try to run env HOME=homedir cib --config not-yaml.yaml config
 given a Radicle node, with CI configured with not-yaml.yaml and adapter dummy.sh
 when I try to run cib --config not-yaml.yaml config
 then command fails
 then stderr contains "failed to parse configuration file as YAML: not-yaml.yaml"
 ~~~

@@ -400,14 +374,11 @@ handled by a dedicated system, such as `systemd`.

 _Who:_ `cib-devs`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 when I run synthetic-events synt.sock --log log.txt
 given file broker.yaml
 when I try to run bash radenv.sh RAD_SOCKET=synt.sock cib --config broker.yaml insert
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 given the Radicle node emits a refsUpdated event for xyzzy
 when I run ./env.sh synthetic-events synt.sock event.json --log log.txt
 when I try to run ./env.sh cib --config broker.yaml insert
 then command is successful
 ~~~

@@ -428,15 +399,11 @@ an object id of all zeros. This should be sufficiently impossible to

 happen in real life.
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given file broker.yaml
 when I run synthetic-events synt.sock --log synt.log
 when I try to run bash radenv.sh RAD_SOCKET=synt.sock cib --config broker.yaml insert
 when I run cat synt.log
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 given the Radicle node emits a refsUpdated event for xyzzy
 when I run ./env.sh synthetic-events synt.sock event.json --log log.txt
 when I try to run ./env.sh cib --config broker.yaml insert
 then command is successful
 when I run cibtool --db ci-broker.db run list
 then stdout is empty

@@ -453,18 +420,14 @@ _Why:_ This is useful for diagnosis, if nothing else.

 _Who:_ `cib-devs`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 when I run bash radenv.sh cibtool --db x.db run add --repo testy --branch main --commit HEAD --failure
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 given a directory reports
 when I run bash radenv.sh cibtool --db x.db report --output-dir reports
 when I run ./env.sh cibtool --db x.db run add --repo xyzzy --branch main --commit HEAD --failure
 when I run ./env.sh cibtool --db x.db report --output-dir reports
 then file reports/index.html exists
 then file reports/index.html contains "testy"
 then file reports/index.html contains "xyzzy"
 ~~~
 This doesn't check that there is a per-repository HTML file, because

@@ -481,20 +444,16 @@ error output. This makes it easier to debug adapter problems.

 _Who:_ `adapter-devs`, `node-ops`
 ~~~scenario
 given an installed CI broker
 given a CI adapter adapter.sh from dummy.sh
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 given the Radicle node emits a refsUpdated event for xyzzy
 when I run ./env.sh synthetic-events synt.sock event.json --log log.txt
 when I run bash radenv.sh cibtool --db ci-broker.db trigger --repo testy --ref main --commit HEAD
 when I run bash radenv.sh cibtool --db ci-broker.db event list --json
 when I run ./env.sh cibtool --db ci-broker.db trigger --repo xyzzy --ref main --commit HEAD
 when I run ./env.sh cibtool --db ci-broker.db event list --json
 given file broker.yaml
 given a directory reports
 when I run bash radenv.sh cib --config broker.yaml queued
 when I run ./env.sh cib --config broker.yaml queued
 then stderr contains "Mordor"
 ~~~

@@ -508,18 +467,12 @@ _Why:_ This allows controlling how much log spew log admins have to see.

 _Who:_ `node-ops`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given file broker.yaml
 given a directory reports
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 when I run bash radenv.sh cib --config broker.yaml config
 when I run ./env.sh cib --config broker.yaml config
 then stderr contains "CI broker starts"
 when I run bash radenv.sh cib --config broker.yaml --log-level error config
 when I run ./env.sh cib --config broker.yaml --log-level error config
 then stderr is exactly ""
 ~~~

@@ -545,8 +498,8 @@ this scenario that we can run `rad` at all.

 _Who:_ `cib-devs`
 ~~~scenario
 given file radenv.sh
 when I run bash radenv.sh rad --version
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 when I try to run rad --version
 then command is successful
 ~~~

@@ -607,7 +560,7 @@ time: if the time is too short, the scenario fails spuriously, and if

 it's very long, the scenario takes longer than necessary.
 ~~~scenario
 given an installed CI broker
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 then file synt.sock does not exist

@@ -644,7 +597,7 @@ work of multiple processes, either.

 _Who:_ `cib-devs`
 ~~~scenario
 given an installed CI broker
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 then file count.db does not exist
 when I run cibtool --db count.db counter show
 then stdout is exactly "0\n"

@@ -796,9 +749,9 @@ count to a desired goal. The script then verifies that everything went

 correctly.
 ~~~scenario
 given an installed CI broker
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given file count.sh
 when I run env bash -x count.sh 100 10
 when I run bash -x count.sh 100 10
 then stdout contains "OK\n"
 ~~~

@@ -879,15 +832,13 @@ itself for this test, but the id shouldn't matter, it just needs to

 be of the correct form.
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 when I run cibtool --db x.db event list
 then stdout is empty
 when I run bash radenv.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD --id-file id.txt
 when I run ./env.sh cibtool --db x.db event add --repo xyzzy --ref main --commit HEAD --base HEAD --id-file id.txt
 when I run cibtool --db x.db event show --id-file id.txt
 then stdout contains "rad:"

@@ -910,20 +861,18 @@ operator wants to prevent many CI runs from happening.

 _Who:_ `cib-devs`, `node-ops`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository testy in the Radicle node
 when I run cibtool --db x.db event list
 then stdout is empty
 when I run bash radenv.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run bash radenv.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run bash radenv.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run bash radenv.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run bash radenv.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run bash radenv.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run ./env.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run ./env.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run ./env.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run ./env.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run ./env.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run ./env.sh cibtool --db x.db event add --repo testy --ref main --commit HEAD --base HEAD
 when I run cibtool --db x.db event remove --all
 when I run cibtool --db x.db event list

@@ -941,7 +890,8 @@ to be able to do this cleanly.

 _Who:_ `cib-devs`
 ~~~scenario
 given an installed CI broker
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 when I run cibtool --db x.db event list
 then stdout is empty

@@ -962,12 +912,10 @@ _Who:_ `cib-devs`

 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 when I run bash radenv.sh cibtool --db x.db trigger --repo testy --ref main --commit HEAD --id-file id.txt
 when I run ./env.sh cibtool --db x.db trigger --repo xyzzy --ref main --commit HEAD --id-file id.txt
 when I run cibtool --db x.db event show --id-file id.txt
 then stdout contains "rad:"

@@ -984,17 +932,17 @@ _Why:_ This is primarily needed for testing.

 _Who:_ `cib-devs`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 given the Radicle node emits a refsUpdated event for xyzzy
 when I run ./env.sh synthetic-events synt.sock event.json --log log.txt
 when I run cibtool --db x.db run list
 then stdout is empty
 when I run bash radenv.sh cibtool --db x.db run add --id xyzzy --repo testy --branch main --commit main --triggered
 when I run ./env.sh cibtool --db x.db run add --id runny --repo xyzzy --branch main --commit main --triggered
 when I run cibtool --db x.db run list --json
 then stdout contains "xyzzy"
 then stdout contains "runny"
 then stdout contains ""state": "triggered""
 ~~~

@@ -1007,17 +955,15 @@ _Why:_ This is primarily needed for testing.

 _Who:_ `cib-dev`.
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 when I run cibtool --db x.db run list
 then stdout is empty
 when I run bash radenv.sh cibtool --db x.db run add --repo testy --url https://x/1 --branch main --commit HEAD --running
 when I run ./env.sh cibtool --db x.db run add --repo xyzzy --url https://x/1 --branch main --commit HEAD --running
 when I run cibtool --db x.db run list --json
 then stdout contains ""repo_name": "testy""
 then stdout contains ""repo_name": "xyzzy""
 then stdout contains ""state": "running""
 ~~~

@@ -1032,15 +978,13 @@ _Why:_ This is primarily needed for testing.

 _Who:_ `cib-dev`.
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 when I run cibtool --db x.db run list
 then stdout is empty
 when I run bash radenv.sh cibtool --db x.db run add --id xyzzy --repo testy --branch main --commit HEAD --success
 when I run ./env.sh cibtool --db x.db run add --id runny --repo xyzzy --branch main --commit HEAD --success
 when I run cibtool --db x.db run list --json
 then stdout contains ""state": "finished""
 then stdout contains ""result": "success""

@@ -1057,15 +1001,13 @@ _Why:_ This is primarily needed for testing.

 _Who:_ `cib-dev`.
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository testy in the Radicle node
 when I run cibtool --db x.db run list
 then stdout is empty
 when I run bash radenv.sh cibtool --db x.db run add --id xyzzy --repo testy --branch main --commit HEAD --failure
 when I run ./env.sh cibtool --db x.db run add --id xyzzy --repo testy --branch main --commit HEAD --failure
 when I run cibtool --db x.db run list --json
 then stdout contains ""state": "finished""
 then stdout contains ""result": "failure""

@@ -1084,15 +1026,13 @@ _Why:_ This is primarily needed for testing.

 _Who:_ `cib-dev`.
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository testy in the Radicle node
 when I run cibtool --db x.db run list
 then stdout is empty
 when I run bash radenv.sh cibtool --db x.db run add --id x --repo testy --branch main --commit HEAD --triggered
 when I run ./env.sh cibtool --db x.db run add --id x --repo testy --branch main --commit HEAD --triggered
 when I run cibtool --db x.db run list
 then stdout has one line
 when I run cibtool --db x.db run show x

@@ -1134,24 +1074,22 @@ Note that we verify both lookup by name and by repository ID, and by

 `cibtool event add` and `cibtool trigger`, to cover all the cases.
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository testy in the Radicle node
 when I try to run bash radenv.sh cibtool --db x.db event add --repo missing --ref main --commit HEAD --base c0ffee
 when I try to run ./env.sh cibtool --db x.db event add --repo missing --ref main --commit HEAD --base c0ffee
 then command fails
 then stderr contains "missing"
 when I try to run bash radenv.sh cibtool --db x.db event add --repo rad:z3byzFpcfbMJBp4tKYyuuTZiP8WUB --ref main --commit HEAD --base c0ffee
 when I try to run ./env.sh cibtool --db x.db event add --repo rad:z3byzFpcfbMJBp4tKYyuuTZiP8WUB --ref main --commit HEAD --base c0ffee
 then command fails
 then stderr contains "rad:z3byzFpcfbMJBp4tKYyuuTZiP8WUB"
 when I try to run bash radenv.sh cibtool --db x.db trigger --repo missing --ref main --commit HEAD --id-file id.txt
 when I try to run ./env.sh cibtool --db x.db trigger --repo missing --ref main --commit HEAD --id-file id.txt
 then command fails
 then stderr contains "missing"
 when I try to run bash radenv.sh cibtool --db x.db trigger --repo rad:z3byzFpcfbMJBp4tKYyuuTZiP8WUB --ref main --commit HEAD --id-file id.txt
 when I try to run ./env.sh cibtool --db x.db trigger --repo rad:z3byzFpcfbMJBp4tKYyuuTZiP8WUB --ref main --commit HEAD --id-file id.txt
 then command fails
 then stderr contains "rad:z3byzFpcfbMJBp4tKYyuuTZiP8WUB"

@@ -1168,17 +1106,12 @@ useful for gathering data for trying out event filters.

 _Who:_ `cib-devs`, `node-ops`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given file refsfetched.json
 given file set-rid
 when I run bash radenv.sh env HOME=../homedir python3 set-rid refsfetched.json testy
 when I run synthetic-events synt.sock refsfetched.json --log log.txt
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 given the Radicle node emits a refsUpdated event for xyzzy
 when I run ./env.sh synthetic-events synt.sock event.json --log log.txt
 when I run bash radenv.sh cibtool event record --output events.json
 when I run ./env.sh cibtool event record --output events.json
 then file events.json contains ""type":"refsFetched""
 ~~~

@@ -1194,18 +1127,12 @@ It's also helpful for CI broker developers as a development tool.

 _Who:_ `cib-dev`, `node-ops`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given file refsfetched.json
 given file set-rid
 when I run bash radenv.sh env HOME=../homedir python3 set-rid refsfetched.json testy
 when I run synthetic-events synt.sock refsfetched.json --log log.txt
 when I run bash radenv.sh cibtool event record --output node-events.json
 when I run bash radenv.sh cibtool event ci --output ci-events.json node-events.json
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 given the Radicle node emits a refsUpdated event for xyzzy
 when I run ./env.sh synthetic-events synt.sock event.json --log log.txt
 when I run ./env.sh cibtool event record --output node-events.json
 when I run ./env.sh cibtool event ci --output ci-events.json node-events.json
 when I run cat ci-events.json
 then file ci-events.json contains "BranchUpdated""
 ~~~

@@ -1221,18 +1148,13 @@ event filters work as they expect.

 _Who:_ `cib-dev`, `node-ops`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given file refsfetched.json
 given file set-rid
 when I run bash radenv.sh env HOME=../homedir python3 set-rid refsfetched.json testy
 when I run synthetic-events synt.sock refsfetched.json --log log.txt
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository xyzzy in the Radicle node
 given the Radicle node emits a refsUpdated event for xyzzy
 when I run ./env.sh synthetic-events synt.sock event.json --log log.txt
 when I run bash radenv.sh cibtool event record --output node-events.json
 when I run bash radenv.sh cibtool event ci --output ci-events.json node-events.json
 when I run ./env.sh cibtool event record --output node-events.json
 when I run ./env.sh cibtool event ci --output ci-events.json node-events.json
 given file allow.yaml
 when I run cibtool event filter  allow.yaml ci-events.json

@@ -1292,16 +1214,10 @@ any events, so `cib` just terminates at once. All of this will work,

 when properly set up.
 ~~~scenario
 given an installed CI broker
 given a CI adapter adapter.sh from dummy.sh
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given file broker.yaml
 given a directory reports
 when I run bash radenv.sh cib --config broker.yaml queued
 when I run ./env.sh cib --config broker.yaml queued
 then stderr contains "CI broker starts"
 then stderr contains "CI broker ends successfully"

@@ -1321,10 +1237,8 @@ We check this by running the CI broker without a local node. This is

 an error it can't recover from.
 ~~~scenario
 given an installed CI broker
 given file broker.yaml
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 when I try to run env RAD_HOME=/does/not/exist cib --config broker.yaml queued
 then stderr contains "CI broker starts"
 then stderr contains "CI broker ends in unrecoverable error"
 ~~~

@@ -1346,15 +1260,10 @@ monitoring system.

 _Who:_ `node-ops`
 ~~~scenario
 given an installed CI broker
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given file broker.yaml
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a directory reports
 when I run bash radenv.sh cib --config broker.yaml queued
 when I run cib --config broker.yaml queued
 then file reports/status.json exists
 when I run jq .event_queue_length reports/status.json

@@ -1399,21 +1308,16 @@ the Git commit identifiers instead. In any case, this scenario needs

 to be updated when a new release is made.
 ~~~scenario
 given an installed CI broker
 given a CI adapter adapter.sh from dummy.sh
 given file radenv.sh
 given file setup-node.sh
 when I run bash radenv.sh bash setup-node.sh
 given a Radicle node, with CI configured with broker.yaml and adapter dummy.sh
 given a Git repository testy in the Radicle node
 given file broker.yaml
 given file verify-upgrade
 given a directory reports
 when I touch file run-list.txt
 when I run bash radenv.sh bash -x verify-upgrade run-list.txt 535b1592904125fbe62c3c8c383d7741d9f432ac
 when I run bash radenv.sh bash -x verify-upgrade run-list.txt 869b451728d16719b560df142b2d901cbaf3764c
 when I run bash radenv.sh bash -x verify-upgrade run-list.txt HEAD
 when I run ./env.sh bash -x verify-upgrade run-list.txt 535b1592904125fbe62c3c8c383d7741d9f432ac
 when I run ./env.sh bash -x verify-upgrade run-list.txt 869b451728d16719b560df142b2d901cbaf3764c
 when I run ./env.sh bash -x verify-upgrade run-list.txt HEAD
 ~~~
 ~~~{#verify-upgrade .file .sh}

@@ -1454,6 +1358,7 @@ nl "$config"

 # from there to avoid having to fetch things from the network.
 rm -rf ci-broker html
 mkdir ci-broker html
 export SRCDIR="$CARGO_MANIFEST_DIR"
 (cd "$SRCDIR" && git archive "$VERSION") | tar -C ci-broker -xf -
 # Do things in the exported CI broker source tree. Capture stdout to a