Open pc-coder opened 2 years ago
The main barrier to new platforms is webhooks.
With GitHub, apps get webhook automatically provisioned.
With GitLab, we use the "system" hook to get a firehose of all repo events.
For other platforms, we'd need to either (a) have a system for automatically provisioning webhooks, or (b) require users to configure webhooks for every project/repository, or (c) not have them at all.
The further challenge with (a) is that adding webhooks generally requires admin privileges, which is undesirable to have in Renovate.
Were webhooks the reason why you were interested in this product? Or just having a stateful job queue is enough benefit for you?
Webhooks were actually secondary for us.
Instead of manually maintaining and setting up monitoring for cron jobs or CI jobs, we were looking for a simpler solution.
So, our requirements are:
Excluding webhook, the other drawback that we are seeing right now is Horizontal Scaling. If we use autodiscoverFilter and run multiple worker instances, we again lose the single source of truth(Dashboard feature, if it's available) and will have to maintain multiple workers then instead of cron jobs.
The app dashboard is not part of whitesource/renovate (it's very much wedded to netlify.com currently and not able to be self-hosted).
Secondly automated/horizontal scaling is not included either.
FWIW, Gitea does support "system" webhooks similar to Gitlab, so might just be a case of implementing something that can parse the event data?
Also the webhook payload is compatible with the GitHub payload. Gitea / Forgejo also support the same secret handling for payload verification.
Please update Title to include Forgejo 🙃 I've closed my issue in favor of this older one.
I can see currently only GitHub and GitLab are supported. Are there any plans to support gitea in the near future? Would it make sense to write a gitlab -> gitea translator API in case there are none?