| I'm quite passioned about CI/CD and working in this field for the last 7 years. I'm keeping a close eye on jenkins, tekton, circleci, travis, github actions, gitlab etc. and never ever heard about earthly. Btw. one thing the person doesn't get: Everyone wants to have fast and reliable builds but no one cares. No one. CI/CD Systems in a developers eye are blackboxes. They don't care. And its already a solved problem somehow. I was waiting for Jenkins X to happen (something like jenkins working nicely in a cloud native way because Jenkins Plugins!) but that didn't happen. What happend instead is Github Actions. Holy shit are Github Actions good. Srsly. GitLab stuff was slow and effort. GitHub Actions just do what they should do 99% of the time. If you do not have a huge build, you will not care about your CI/CD System and everyone who has real build issues, has to solve it by another strategy than just switching the build system. |
In GitHub actions, the process is super abstracted and opaque. It doesn't really match anything I've used before and knowledge of unix doesn't help top much. I can't really reason what will happen, things are the way they are because that's how GitHub actions work, rather than something I can work out.
I can see a certain part of the build is slow, I know how I'd fix it if I were on Jenkins land, but here it's just too abstracted. I end up just googling and finding someone else with the same problem and copying how they fixed it.
I do agree that gitlab is worse somehow than GitHub actions.