3 ms·
The only part of the Earthly pitch that resonated with me was the ability to run the CI locally. When debugging your CI, it is just faster to find problems whe
by jnwatson 3y ago
The only part of the Earthly pitch that resonated with me was the ability to run the CI locally. When debugging your CI, it is just faster to find problems when you can run on your own box.
I have a gnarly GitHub Actions script that took forever to get right because the debug cycle was 10 minutes long.
- fireflash38 3y agoThat's one of my biggest complaints about gitlab-ci. Theres basically no way to debug complex rules without just running it. They've got a way now to simulate for default branch, but that's like bare minimum necessary. No way to simulate based on vars or anything else. And no way to try locally, just gotta fucking send it live.
- ianwalter 3y agoI feel you on that one. There is also Act (https://github.com/nektos/act https://github.com/nektos/act) and Dagger.io.
- jnwatson 3y agoI have a very complicated script and Act didn't work on it.
- smaudet 3y agoYeah, the faster but is also a bit of a non-seller, they have to integrate the world/deal with bad build times that can't easily be parallelized (what if there are no modular dependencies, that your tool can understand?) except by tools that have nothing to do with their product. But there have been many times when debugging a CI has been necessary, having to figure out what has gone wrong on a remote system is often an issue...ofc often the remote system is itself the problem...