drone VS Laminar

Drone (https://github.com/harness/drone) shell's all codes are deleted and replaced with new project (gitness) to retain Github Stars. What do you think?

I went to check on this, and it seems that https://github.com/harness/drone redirects to harness/gitness. I'm now very confused.

You can check the drone license or sentry license.

To use github my code would have to leave my server. I can build it myself using woodpecker. I used drone.io till they were bought out and went closed source then migrated to woodpecker-ci

A lot of people on reddit seem to recommend gitlab, or drone.io, but if you get on indeed and search for jobs there are tens of thousands of posts looking for people who know Jenkins and only a tiny fraction of job listings interested in any other ci framework. Is it worth investing time into anything else? It's my decision and while the other options seem more friendly I don't see any point in learning them if I'm not going to be able to use them in the future.

I personally use drone CI (https://drone.io) with the DroneExternalConfig plugin (https://github.com/0x1a8510f2/DroneExternalConfig).

Gitea + drone.io is what I am using. Very happy with the solution.

No 5000 build limit if you use Gitea/Gogs Ref: https://github.com/harness/drone/blob/master/service/license/load.go

I really should migrate to Gitea + drone.io

I'm really embarassed to say that I love docker-compose over K8s for its simplicity & effectiveness.But tools are reallly lacking.drone.io is like a docker-compose.yml. Simple, effictive & beautiful.

*Laminar - I like how simple this is

I use Laminar CI for this: https://laminar.ohwg.net/

Delve into Laminar would be my suggestion.

I like Laminar as a lightweight, self-hosted CI solution.

For a lightweight solution, I like to recommend Laminar CI.

Laminar

Laminar is a lightweight and modular CI system licensed under GPLv3. I like that it allows me to build the CI solution that fits my given use case the best.

I find Laminar quite interesting in this space. It might help you too to build your own lightweight CI solution that does exactly what your use case requires.

My continuous integration / continuous deployoment system is based on Laminar CI (blog post series). It serves various purposes:

jftr: There is another project with this name which is deceptively similar, but also very different… (quoting the README): Laminar is a lightweight and modular Continuous Integration service for Linux. It is self-hosted and developer-friendly, eschewing a configuration UI in favour of simple version-controllable configuration files and scripts.