Are you self-hosting code in Forjego by any chance? If yes, there's an integrated system called "actions"[1].
Jenkins is popular but complex. I would look elsewhere, woodpeckerCI looks like a good solution but I don't have direct experience with it.
I've worked with Tekton in the past, but it's tailored around kubernetes, e.g. a good for k3s (self-hosted k8s cluster).
If you're not self-hosting and you use something like github, you need to either leave an HTTP server open to the internet (insecure) or use something like ngrok, smee.io, cloudflare tunnel, hookdeck, etc. These tools will manage to forward the webhook in a secure way to the internal system.
Github Actions runner can be self-hosted as well! Microsoft tried to curb it for a while by making self-hosted runner minutes paid as well, but quickly walked that back.
Do note that Github Actions have been the target of like 50 different attacks and I would not combine publicly hosted code with your own runners, as without proper sandboxing it can lead to anybody executing any code on your machine just by opening a PR (might have been fixed since last I heard, but the general vibe stands).
Github does provide to connect your self host runners.
But if you ever needed to do this offline like localhost only you can use Gitea (has its own Gitea Actions as Github local) and connect it with Woodpecker CI.
Are you self-hosting code in Forjego by any chance? If yes, there's an integrated system called "actions"[1].
Jenkins is popular but complex. I would look elsewhere, woodpeckerCI looks like a good solution but I don't have direct experience with it.
I've worked with Tekton in the past, but it's tailored around kubernetes, e.g. a good for k3s (self-hosted k8s cluster).
If you're not self-hosting and you use something like github, you need to either leave an HTTP server open to the internet (insecure) or use something like ngrok, smee.io, cloudflare tunnel, hookdeck, etc. These tools will manage to forward the webhook in a secure way to the internal system.
[1]: https://forgejo.org/docs/latest/admin/actions/
Take the time to read up on CI/CD
Lots of different options, hosted and self hosted.
Github actions and GitLab are two of the more common ones, the latter is self hosted but the former is the dominant one if CV skills is needed
Github Actions runner can be self-hosted as well! Microsoft tried to curb it for a while by making self-hosted runner minutes paid as well, but quickly walked that back.
Do note that Github Actions have been the target of like 50 different attacks and I would not combine publicly hosted code with your own runners, as without proper sandboxing it can lead to anybody executing any code on your machine just by opening a PR (might have been fixed since last I heard, but the general vibe stands).
I use webhooks to argo events that trigger argo workflows on a small k3s cluster on my desk. You could do the same even with a single node cluster.
You could run Woodpecker, maybe? https://woodpecker-ci.org
https://github.com/02zerocool/truth-benchmark https://github.com/02zerocool
not sure if that would help or not but i will share it just incase.
Jenkins is perfect for this.
Github lets you start up a self-hosted runner.
Jenkins
Github does provide to connect your self host runners.
But if you ever needed to do this offline like localhost only you can use Gitea (has its own Gitea Actions as Github local) and connect it with Woodpecker CI.
https://gittea.dev/ https://woodpecker-ci.org/
good luck.