Woodpecker is a fork of Drone version 0.8, this is because the Drone CI license was changed after the 0.8 release from Apache 2 to a proprietary license. Woodpecker is based on this latest freely available version.
GitHub Actions hands down. Huge amount of community-provided actions, easy to get started, lots of ways to reuse workflows or parts of workflows. Perfect integration with GitHub obviously.
I just implemented my first CI action on GitHub two days ago and can't wait to do it again.
You get deep integration that is hard (at least for me historically) to get anywhere else.
I have a monorepo, with builds and deploys for each directory, so if I make changes to only 1 of my n-many directories, it only builds and deploys for that 1.
But with things like Vercel, Netlify, Render, Heroku (rip lol), and others having built in CI, it leads to interesting conversations around centralized CI (GitHub Actions) vs decentralized CI (aforementioned vendors).
I hadn't realized the difference between the two before now, but they have advantages and disadvantages.
I'm actually in process of moving our team's CI/CD back to jenkins from github actions. I can see github actions working well for a startup to midsize company but my current project working with a big enterprise company with corporate networks and limitations has made it a nightmare.
if you have a jenkins working well for team's daily CI with different tasks/plugins, then there are 'new' things come out. it is fun to try them,
not sure if it is really worthy to move to adopt the 'new' approach as it trends?
not against adopting 'new' approaches, while...
it is nice to put that on resume tho for sure... :-)
Readit News
Woodpecker is a fork of Drone version 0.8, this is because the Drone CI license was changed after the 0.8 release from Apache 2 to a proprietary license. Woodpecker is based on this latest freely available version.
You get deep integration that is hard (at least for me historically) to get anywhere else.
I have a monorepo, with builds and deploys for each directory, so if I make changes to only 1 of my n-many directories, it only builds and deploys for that 1.
But with things like Vercel, Netlify, Render, Heroku (rip lol), and others having built in CI, it leads to interesting conversations around centralized CI (GitHub Actions) vs decentralized CI (aforementioned vendors).
I hadn't realized the difference between the two before now, but they have advantages and disadvantages.
With Buildkite I set up a 40/mo Hertzner box with a ton of power, getting about 20x throughput for the price. Not affiliated with them in any way.
Overall the interface is nicer I’d say, but the dedicated machine setup did throw me for a few loops.
https://docs.github.com/en/actions/hosting-your-own-runners/...
if you have a jenkins working well for team's daily CI with different tasks/plugins, then there are 'new' things come out. it is fun to try them, not sure if it is really worthy to move to adopt the 'new' approach as it trends?
not against adopting 'new' approaches, while... it is nice to put that on resume tho for sure... :-)