Products · Pattern or everyday thing
CI/CD
Raised as a usability problem by 10 people on Hacker News over 12 years (2014–2025), in 9 threads.
People raised many different problems with CI/CD, but no single problem has yet been raised by 3 people in 3 different months and threads.
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 10 complaints
- Features often fail or behave unexpectedly, requiring arcane domain knowledge to get working2025-12-15
- Article is confusing because the author is too close to the problem2023-09-12
- Test output so flooded with WARNING and ERROR logs it became unusable2023-05-18
- Setting up deployment pipelines requires tedious, hard-to-write YAML configuration2022-05-03
- Must repeatedly commit and update CI config to debug broken pipelines2022-03-30
- A failed 3-hour build must be restarted from scratch, which is very annoying2022-03-30
- YAML configuration in a CI system is very confusing to understand2021-08-15
- Errors only surface after minutes of running, with no pre-validation or linting2020-04-12
- Config can only be tested by committing and pushing, no way to try it first2018-03-22
- Build status icons were non-obvious, so developers weren't paying attention to them2014-08-27