We're moving continuous integration back to developer machines
world.hey.com
world.hey.com
De-centralizing test running also makes it difficult/impossible to e.g. collect test analytics (like Buildkite can do natively) to help gain insight into flaky tests, how code changes impact test duration, etc., and visualize those things over time, especially if developers are using non-homogenous hardware.
That, and if your tests are not being run in CI, then what enforces that tests run and pass before a deploy occurs? Losing that guarantee is not great IMO.
You will run into huge issues with developers machines all being different. Most of the point of CI is to run these things asynchronously in isolation.
A recent HN submission [0] links to a post in a series about reducing development friction. I do recommend reading the whole thing, but one post is specifically about not using CI [1].
0 - https://news.ycombinator.com/item?id=38831991
1 - https://github.com/aaronjensen/software-development/blob/mas...