Hacker News Reader

Teams not respecting their CI systems will end up shipping slow, low quality code.

That being said, the article referenced seemed to be talking about very basic and straightforward things. A far more nuanced and pragmatic perspective is required to get CI systems to work nicely with today’s CD (e.g. Argo, Flux, Spinnaker) and orchestration systems (e.g. k8s).

View on HN

Or individual developers will circumvent CI out of frustration with it, completely defeating its purpose and making it a waste of money.

alas... this is very true. I still think a well maintained CI system which actively prunes flaky tests can be a great productivity booster for the team. Doing so does require serious and continued investment though, which most teams aren't willing to make.

Reply on news.ycombinator.com