drone VS goreleaser

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.

I also got my eyes on GoReleaser, which I will use in my (Go) projects.

With "xq", I went even further and automated the release process using GoReleaser. To publish a new release, the only thing I need is to create and push the Git tag. The corresponding GitHub Action will trigger a release process, and GoReleaser prepares the binaries and changelog based on declared conventions. The result has a high level of predictability, and no manual work is required.

Things I can't live without in a new Go project in no particular order:

- https://github.com/golangci/golangci-lint - meta-linter

- https://goreleaser.com - automate release workflows

- https://magefile.org - build tool that can version your tools

- https://github.com/ory/dockertest/v3 - run containers for e2e testing

- https://github.com/ecordell/optgen - generate functional options

- https://golang.org/x/tools/cmd/stringer - generate String()

- https://mvdan.cc/gofumpt - stricter gofmt

- https://github.com/stretchr/testify - test assertion library

- https://github.com/rs/zerolog - logging

- https://github.com/spf13/cobra - CLI framework

FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb

We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers

Goreleaser is nice. https://goreleaser.com/

I use goreleaser for packaging my binaries. I'm not currently doing RPM, but it does a lot of services and if you don't hunker down on a single solution, it might help with keeping your releases up to date/in sync.

There's some packaging issues, for example, we've always wanted to publish deb/rpm packages, but never got around to adding it to either promu or completely switching our build tooling over to GoReleaser.