I am new to DevOps. when I searched for CI/CD tools to learn I came to know about Jenkins. At the same time, The debates around Jenkins' relevance in today's dynamic ecosystem are divided, with opinions ranging from
Option 1: Jenkins is still the king of the CI/CD market
Option 2: Jenkins is obsolete, new tools (Github action, GitLab CI/CD, Argo-CD , GoCD, etc) are better
I understand each tool has its advantages and disadvantages. and not all people will like all the tools.
My questions are, from a neutral prospective
Q1. Is Jinkins still relevant for the Job market?
Q2. Do companies for new projects use Jenkins or is it only for old-existing pipelines?
Q3. what if not Jenkins, what other alternative will be the answer?
Top comments (2)
Hey! I've been a DevOps for 7 years and this is based in my experience, so don't take this as the absolute truth π for that reason they'll be short answers.
Q1: not to me, but that depends if the company you're applying to is currently using it or not. However, I think using it gives you a nice understanding of what pipelines are and the concepts like runners, steps, jobs, flows...
Q2: I would say no, but again it depends on the company because a self hosted Jenkins would be probably cheaper and more powerful in the right hands. If the company is going after new technologies and practices it shouldn't be the first option to start
Q3: normally GitHub actions, circleci or other companies. The catch to save some money is to use self hosted runners
Hope they're useful
Thanks for your reply. Really appreciate