mirror of
https://seed.radicle.dev/rad:zwTxygwuz5LDGBq255RA2CbNGrz8.git
synced 2026-10-18 19:30:29 +08:00
feat: output trigger event to stdout, file
Signed-off-by: Lars Wirzenius <liw@liw.fi>
This commit is contained in:
@@ -1789,6 +1789,33 @@ then stdout contains "main"
|
||||
~~~
|
||||
|
||||
|
||||
## Can output trigger message for a CI run
|
||||
|
||||
_Want:_ The `cibtool` command can output the CI event to trigger a CI
|
||||
run to the standard output or a file.
|
||||
|
||||
_Why:_ This is helpful for debugging the CI broker at least.
|
||||
|
||||
_Who:_ `cib-devs`
|
||||
|
||||
|
||||
~~~scenario
|
||||
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 ./env.sh cibtool --db x.db trigger --repo xyzzy --stdout
|
||||
then stdout contains "rad:"
|
||||
then stdout contains "main"
|
||||
|
||||
when I run ./env.sh cibtool --db x.db trigger --repo xyzzy --output trigger.json
|
||||
then file trigger.json contains "rad:"
|
||||
then file trigger.json contains "main"
|
||||
|
||||
when I run cibtool --db x.db event list
|
||||
then stdout is empty
|
||||
~~~
|
||||
|
||||
|
||||
## Add information about triggered run to database
|
||||
|
||||
_Want:_ `cibtool` can add information about a triggered CI run.
|
||||
|
||||
Reference in New Issue
Block a user