Git CI DVM

[alexgleason]

I just wanted to say that it's possible to submit a DVM request in a git post-receive hook to run a CI job, and then build some sort of weird bridge with git web services to display the result.

[alexgleason]

@DanConwayDev This is how you should do CI in the git stuff you're building. Just display DVM results that point to the commit. The CI job itself doesn't have to be integrated, just a UI to display the results. Then any DVM can provide it.

[DanConwayDev]

Thanks! I was thinking a request to run a CI job could be raised via:

1. a service that watches for patch events and immediately makes CI DVM requests on behalf of maintainers
2. a prompt after a proposal has been submitted in ngit send
3. a button on gitworkshop.dev to request CI for a particular patch or latest version of proposal

The issue with a git post-receive hook is that it requires contributors to have write access to the git server.

I have not thought to deeply about CI DVMs but there is a trust issue. Why should we trust that the output is not either malicious or faked to save computing resource (a copy of a previous CI run).

Is it possible to validate, or partially validate, that a job has been run?

[alexgleason]

You can choose which DVM to use as part of the request. I imagine you could let the user configure a specific DVM in each project for future runs. The user would just need to pick a reputable one.

[alexgleason]

It would be really interesting to take an existing CI runner such as GitLab Runner and bridge it to Nostr. With some DVM translation layer in between.

[DanConwayDev]

That would be great! I'm ashamed to say I haven't looked closely enough at DVMs. I'm looking forward to getting my hands dirty. Unless of course some body beats me to it, which I certainly wouldn't object to.