SourceHut builds.sr.ht
Shares rank 17 of 20 CI/CD services by recommenders
People recommend it for simple shell-based builds, SSH access into failed jobs, and triggering jobs by submitting a YAML file. Critics note it is barebones compared with GitHub Actions.
People recommend it for simple shell-based builds, SSH access into failed jobs, and triggering jobs by submitting a YAML file. Critics note it is barebones compared with GitHub Actions.
6 people gave an opinion
- recommend it
- 5
- criticize it
- 1
- approval share
- 83%
Recommended in 4 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- 5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 4 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
SSH into failed job's VM to debug
“It is trivial do debug failing state there since you can ssh into the job's vm.”
Comment from 5 Feb 2026 in “GitHub Actions Is Slowly Killing Your Engineering Team” “When the build fails, you can SSH into the machine and debug it from there.”
Comment from 14 Jan 2026 in “I Hate GitHub Actions with Passion”
What people warn about
Each mark is one comment
Barebones, lacking features versus GitHub Actions
“is pretty barebones / lacking compared to GH/GitHub actions”
Comment from 29 Apr 2026 in “Ghostty is leaving GitHub”
Other CI/CD services people recommend
The four most recommended other CI/CD services, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| GitHub Actions | 234 | 741 | 24% | 12 | 2 yrs21 owners | — |
| Jenkins | 67 | 57 | 54% | 9 | — | — |
| GitLab CI | 56 | 25 | 69% | 11 | 3 yrs9 owners | Approved |
| Dagger | 43 | 23 | 65% | 10 | — | — |
| SourceHut builds.sr.htThis page | 5 | 1 | 83% | 4 | — | — |
What people said
All 7 comments that mention it, newest first. Each links to the original comment.
“they should get those leaking keys under control as much as possible.”
“is very simple to use, based on shell scrips, and has some neat features”
“is pretty barebones / lacking compared to GH/GitHub actions”
“It is trivial do debug failing state there since you can ssh into the job's vm.”
“As I said, I really like the SourceHut CI.”
“When the build fails, you can SSH into the machine and debug it from there.”
“A really neat feature is that you can also trigger a job by just submitting a yaml file”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.