refactor(ci-broker.md): rename trigger.json to be more correct

It's a "refsFetched" node event, not a trigger message. The name was
the last remaining remnant of an earlier approach to verifying the CI
broker.

Signed-off-by: Lars Wirzenius <liw@liw.fi>
This commit is contained in:
Lars Wirzenius
2024-07-08 17:35:06 +03:00
parent 0d86c048b9
commit 0e5c1d7dc9
+16 -16
View File
@@ -56,7 +56,7 @@ echo '{"response":"finished","result":"success"}'
This is a node event from the node to signal that some git refs have
changed in repository.
~~~{#trigger.json .file .json}
~~~{#refsfetched.json .file .json}
{
"type": "refsFetched",
"remote": "z6MkgEMYod7Hxfy9qCvDv5hYHkZ4ciWmLFgfvm3Wn1b2w2FV",
@@ -94,10 +94,10 @@ This asks the CI broker to shut down cleanly.
~~~
## Set rid in trigger message
## Set rid in `refsFetched` event
This is a helper script that reads a trigger message and changes its
`rid` field to be the id of the given repository. It also sets the
This is a helper script that reads a `refsFetched` event and changes
its `rid` field to be the id of the given repository. It also sets the
`name` field for updated refs to include the repository ID. It writes
the message back to its file.
@@ -231,11 +231,11 @@ given file setup-node.sh
when I run bash radenv.sh bash setup-node.sh
given an installed synthetic-events
given file trigger.json
given file refsfetched.json
given file shutdown.json
given file set-rid
when I run env HOME=../homedir python3 set-rid trigger.json testy
when I run synthetic-events synt.sock trigger.json shutdown.json --log log.txt
when I run env HOME=../homedir python3 set-rid refsfetched.json testy
when I run synthetic-events synt.sock refsfetched.json shutdown.json --log log.txt
given an installed cib
given a directory reports
@@ -280,11 +280,11 @@ given file setup-node.sh
when I run bash radenv.sh bash setup-node.sh
given an installed synthetic-events
given file trigger.json
given file refsfetched.json
given file shutdown.json
given file set-rid
when I run env HOME=../homedir python3 set-rid trigger.json testy
when I run synthetic-events synt.sock trigger.json shutdown.json --log log.txt
when I run env HOME=../homedir python3 set-rid refsfetched.json testy
when I run synthetic-events synt.sock refsfetched.json shutdown.json --log log.txt
given file adapter.sh from adapter-with-url.sh
when I run chmod +x adapter.sh
@@ -545,9 +545,9 @@ when I run bash radenv.sh bash setup-node.sh
given an installed cib
given an installed synthetic-events
given file trigger.json
given file refsfetched.json
given file shutdown.json
when I run synthetic-events synt.sock trigger.json shutdown.json --log synt.log
when I run synthetic-events synt.sock refsfetched.json shutdown.json --log synt.log
given file broker.yaml
when I try to run bash radenv.sh env RAD_SOCKET=synt.sock cib --config broker.yaml insert
@@ -575,9 +575,9 @@ when I run bash radenv.sh bash setup-node.sh
given an installed cib
given an installed synthetic-events
given file trigger.json
given file refsfetched.json
given file shutdown.json
when I run synthetic-events synt.sock trigger.json shutdown.json --log synt.log --repeat 1000
when I run synthetic-events synt.sock refsfetched.json shutdown.json --log synt.log --repeat 1000
given file broker.yaml
when I try to run bash radenv.sh env RAD_SOCKET=synt.sock cib --config broker.yaml insert
@@ -606,9 +606,9 @@ when I run bash radenv.sh bash setup-node.sh
given an installed cib
given an installed synthetic-events
given file trigger.json
given file refsfetched.json
given file shutdown.json
when I run synthetic-events synt.sock trigger.json shutdown.json --log synt.log
when I run synthetic-events synt.sock refsfetched.json shutdown.json --log synt.log
given file broker.yaml from broker-allow-nothing.yaml
when I try to run bash radenv.sh env RAD_SOCKET=synt.sock cib --config broker.yaml insert