pipeline VS drone

Tekton

Tekton is an open-source framework for creating efficient CI/CD systems. This empowers developers to seamlessly construct, test, and deploy applications across various cloud environments and on-premise setups.

Despite other alternatives like Circle CI, Travis CI, GitLab CI or even self-hosted options using open-source projects like Tekton or Argo Workflow, the reason for choosing GitHub Actions was straightforward: GitHub Actions, in conjunction with the GitHub ecosystem, offers a user-friendly experience and access to a rich software marketplace.

[2]: https://github.com/tektoncd/pipeline/issues/5507#issuecommen...

Drone, or Tekton, Argo Workflows if you’re on k8s

If you want a step up, I would recommend trying out Tekton Pipelines. It’s a very popular ci tool, and it runs on Kubernetes. Yes, this would involve setting up a Kubernetes cluster but please don’t run for the hills! You can setup a Kubernetes cluster and install Tekton on top of it with minimal setup using minikube (see here. This would be a great joint exercise as it will give you a bit of Kubernetes understanding alongside it, and the mechanisms of Tekton are a little trickier than GitHub actions imo. It’s all much the same though.

I've recently found this quote by Kelsey Hightower:

"I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."

Source: https://twitter.com/kelseyhightower/status/85193508753294540...

In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.

My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.

Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?

Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.

Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?

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.