I want to trigger CI runs for some of my radicle repos, on my self-hosted Jenkins. So I'm running a CI broker alongside my node, and I'm using the webhooks adapter to do the triggering.

Not all of my repos have a job in Jenkins right now.

Looking at the broker-adapter protocol, I see that the adapter is always expected to output a "triggered" and "finished" message. I also see that if the broker doesn't receive any output from the adapter, it logs the run as a failure.

In my case, when there is no jenkins job - the repo also doesn't have a webhook configured. So the adapter does trigger, but finds no webhooks configured and therefore triggers no runs. I don't see this as a failure. But the only options currently for the adapter are: a. send triggered / finished messages (which means a job cob is created as well, for a run that didn't happen), b. don't send anything back to the broker (no job is created - which is what I expect - but the broker logs this as a failure, which doesn't match my understanding of what happened),

I wonder if there is room for a "skip" message to be added to this protocol, to allow the broker to know that the adapter didn't error.

Link to zulip thread: https://radicle.zulipchat.com/#narrow/channel/452370-radicle-ci/topic/broker.20-.20adapter.20protocol.20does.20not.20allow.20.22skip.22/near/594595106