That's effectively what we are doing. The webhook receives any "custom properties" you have defined on your repo, the ssh url, and critically, the name of the Action that was run. The receiving server can use all of this to select the appropriate pipeline. Our build server is not containerized.
Sounds like you are assuming that I have a server always running for this stuff? That assumption is wrong. I don’t want to run CI servers. If I had servers always running, I would install Jenkins on them and the problem would be solved.
If you are doing deployments, actions etc does exactly that. Run pure bash commands or whatever.
If you want it for other purposes, you essentially want to run a "server" application but don't want to manage a server. Just use serverless? Write a JS function (or some other languages) and the platform will run it when the event triggers.
1. SaaS CI/CD products, like GitHub Actions,
2. Run your own Jenkins cluster,
3. Figure out how to orchestrate cloud resources to do this for you.
Maybe there are easy options that I’m missing. I don’t really want to create docker containers just to build some program I’m working on.