Remove the automatic trigger for GitHub releases (which was a successful regression run on master). Instead, extend the server/worker interface with a new command, so that a manual invocation of ./worker --release <id> should trigger the release of <id> by the server.
The release is only attempted if <id> corresponds to a finished, successful regression run. Note that this still permits out-of-order releases, i.e. the release of v2 can be triggered before the release of v1.
xrchz
commented
8 months ago
Remove the automatic trigger for GitHub releases (which was a successful regression run on
master). Instead, extend the server/worker interface with a new command, so that a manual invocation of./worker --release <id>should trigger the release of<id>by the server.The release is only attempted if
<id>corresponds to a finished, successful regression run. Note that this still permits out-of-order releases, i.e. the release ofv2can be triggered before the release ofv1.