{"slug": "drone-ci", "name": "Drone CI", "category": "infra", "category_name": "Infrastructure and DevOps", "description": "", "recommenders": 1, "commenters": 2, "warners": 0, "score": 1.131, "rising": -0.33, "first": "2026-02-06", "latest": "2026-08-17", "why": "", "why_is_quote": false, "has_verdict": false, "sentiment": {"recommend": 1, "neutral": 1, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0], "listed": false, "loved": [], "caveat": "", "short_quote": "", "icon": false, "domain": null, "github_repo": null, "official_url": "", "pricing": "", "aliases": ["Drone CI"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 750617570, "item_id": 46913598, "url": "https://news.ycombinator.com/item?id=46913598", "by": "_rwo", "date": "2026-02-06", "stance": "recommend", "quote": "I had good memories about droneci", "excerpt": "The only way this title could be any better is this: Github Actions is slowly KILLING engineering teams /s Said that - every CI sucks one way or another, Github actions is just good enough to fire up a simple job/automation which seems to be majority of use cases anyway? I think fully production CI pipelines will always be complicated in one way or another (proper catching alone is a challenge on it's own); I really ", "context": "", "use_case": "CI", "switched_from": "", "story": "GitHub Actions Is Slowly Killing Your Engineering Team"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["ci"], "compared": [{"slug": "woodpecker-ci", "name": "Woodpecker CI", "co": 2, "switched_from": 0, "switched_to": 1}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49331033", "title": "Ask HN: Alternatives to GitHub", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46908491", "title": "GitHub Actions Is Slowly Killing Your Engineering Team", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {"recommend": 1}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {"neutral": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 789361635, "item_id": 49335102, "url": "https://news.ycombinator.com/item?id=49335102", "by": "KronisLV", "date": "2026-08-17", "stance": "neutral", "quote": "Well there was DroneCI in the middle for a bit there as well", "excerpt": "I also self-hosted GitLab for some years, eventually ended up moving over to Gitea + WoodpeckerCI + Nexus (with Nexus for a while). Well there was DroneCI in the middle for a bit there as well, but Woodpecker is perfectly okay and more free in regards to what you can do. Only thing is that not that much other software out there supports Gitea, for example Kepler only knows about GitHub, GitLab, Jira, Trello and Linea", "context": "", "use_case": "CI", "switched_from": "", "story": "Ask HN: Alternatives to GitHub"}, {"id": 750617570, "item_id": 46913598, "url": "https://news.ycombinator.com/item?id=46913598", "by": "_rwo", "date": "2026-02-06", "stance": "recommend", "quote": "I had good memories about droneci", "excerpt": "The only way this title could be any better is this: Github Actions is slowly KILLING engineering teams /s Said that - every CI sucks one way or another, Github actions is just good enough to fire up a simple job/automation which seems to be majority of use cases anyway? I think fully production CI pipelines will always be complicated in one way or another (proper catching alone is a challenge on it's own); I really ", "context": "", "use_case": "CI", "switched_from": "", "story": "GitHub Actions Is Slowly Killing Your Engineering Team"}]}