Hacker News new | ask | show | jobs
by Klugistiono 1018 days ago
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.

2 comments

That's an interesting perspective. I used to work at a large company with a massive Jenkins setup. The nice thing about Jenkins is that your unix skills translate. It basically just runs a shell script and you can do anything.

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.

GitHub Actions is the same as everything else. It doesn't work any better or worse. But the UI is clunkier, you can do less with it than other systems, it lacked important features forever (still does). The only reason you think it's significantly better is psychological.

The "market" of actions is better than competitors because the incumbent gets an advantage, and it trades on the idea of a generic executable as a 3rd party plugin, unlike other systems that try to force you into a particular language or paradigm. But other systems do this too.

I build enough pipelines in GitLab way to be able to tell you that GitHub Actions is much easier for me to implement.

Its much closer than if you would have a second system like jenkins, i already have access to git and the packages.

I do use much more container images than i did 6 or 10 years ago, that might have something to do with it but nonetheless, i do prefer GitHub Actions.

I also stoped liking GitLab though. The Autodevops was horrendes, the security issues is concerning and plenty of ideas or features are half done. this is also something which changed. I liked GitLab much more than i do now. But looking at the year, i haven't looked at GitLab for at least 2 years now.