onedev VS kubernetes-operator

I'm going to plug https://onedev.io/ its awesome. Its self hosted and has its own tooling for CI/CD. I feel it doesn't get enough love, but I've been using it for years for my own stuff.

I started to develop OneDev (https://onedev.io) since 2013 as an open source project in my spare time. To sustain long-term development of the project, an enterprise edition was released last month, and today it welcomed the first commercial customer. Not a very successful project from monetization point of view, but I enjoyed all the trips developing and maintaining it.

An option I don't see often brought up but I use it myself and love it is https://github.com/theonedev/onedev. It has its own CICD implementation along with a visual interface to configure the tasks. The developers are very responsive when issues are reported, and it has a very good code search engine with symbol recognition.

https://leantime.io/ And https://onedev.io/ (if you want ci/cd as well)

OneDev supports projects.

Recently though, I've seen some awesome packaging of jenkins into a stateless beast that is DRY AF and configurable to the N-th degree. Do your engineering squads argue about which plugins to install, syntax to use or even methods of authenticating into the jenkins instance? Fine give them their own instance... all managed via jenkins-operator in your k8s cluster (as an example).

Possible options considered; Run Jenkins on a master and worker build server on EC2 Run Jenkinsci on Kubernetes with https://github.com/jenkinsci/kubernetes-operator

You mean this operator? https://github.com/jenkinsci/kubernetes-operator