3 ms·
I really really want to use this but it doesn't work with podman which is unfortunately a bit of a blocker. IMO every CI system should be runnable locally, with
by hardwaregeek 4y ago
I really really want to use this but it doesn't work with podman which is unfortunately a bit of a blocker. IMO every CI system should be runnable locally, with minimum effort. Otherwise you end up testing via git push and that's just an ugly development cycle.
This does make me wonder if you could create a sort of "local first CI" where CI is just an extension of local checks. Therefore the CI is just a check that tests that pass locally also pass on a clean machine. Obviously we don't want to run CI locally if it'd take an hour, but on the flip side, if CI takes an hour on a (typically) beefy local dev machine, it'll probably take 2 hours on a remote machine.
- reillyse 4y agoSuper interesting you mention “local first CI”. Have a look at Brisk https://brisktest.com/ https://brisktest.com/ (I’m the author). It’s designed to work “locally” pre-commit, giving you super fast tests, but then when you push you can also use it in your CI/CD pipeline. We achieve the speed with massive concurrency and pre-built environments, it was built as a drop in replacement for your local test runner.
- hardwaregeek 4y agoAwesome! Glad to see people are thinking the same things. I'll definitely check it out.