Jenkins VS GitHub Actions - Which one should you choose?

#jenkins #cloudcomputing #devtools #shortsfeed #github #githubactions

Links 🔗

What other cloud topics should we cover?

[itsjakepage]

That's a fair assessment Phred, thanks for your thoughts. I must admit that if I were to start a project from scratch I would probably go with GitHub actions route. The only thing that still bugs me is that there are so many people and organisations out there that use Jenkins, seem happy enough with it yet are not vocally defending Jenkins in public forums. So when people so vehemently discredit Jenkins I can't help but think that they are probably missing something or potentially overblowing the downsides of the tool, since granted, it is old, but it gets the job done.

[phredlane]

I think you say mature while I say old/antiquated. Jenkins definitely feels like an enterprise tool. I would be surprised to see it in most other environments. Starting a company today with Jenkins seems unlikely and probably a mistake in most cases unless your business is Jenkins-adjacent.

I don't believe there are many common tools used in Jenkins that cannot be replicated in GitHub actions, TravisCI, CircleCI, etc. I believe you're more comfortable with Jenkins more than it's better in any specific way. The same is potentially true in reverse. I'm definitely more of a buy-over-build type. If your company's business is not CI/CD tools, I don't see the value in hosting it locally.

[prettybasic]

If you're hosting your code in gh, Most people nowadays, it would be a crime if you're not leveraging gh actions