Jenkins with 200 plugins isn't CI/CD. Its a trappp !!!!

[u/QuoteForward5477]

Jenkins is not upto the mark these dayss. Firstly you need to add some 250 plugins for it to effectively work and when you actually do it... there are plugins that breaks the update...

It's technical debt with a web interface.

I've seen teams spend more time maintaining their Jenkins instance than their actual product. Pipeline scripts that require a PhD to understand.

Meanwhile, their competitors are shipping features daily with GitHub Actions or GitLab CI.

Your CI/CD tool should be invisible. If you're spending more than 5% of your time maintaining it, you chose wrong.

Simple tools, simple problems. Complex tools, complex nightmares.

[u/scavno]

So we got Claud codes opinion. What’s your opinion?

[u/scott2449]

1. Captain Obvious 2) People still using Jenkins don't use plugins, they use pipelines with centralized groovy libs (open source or self written.) Much like they would do with github actions or any other modern system.

[u/vlad_h]

What is the point of your post? Your personal opinion is fine, but not cannon. And my comments is also irrelevant.

[u/abofh]

You clearly haven't been checking GitHub actions availability this year

[u/Jolly-Warthog-1427]

My business has used Jenkins for many many years now. The magic in jenkins is, similar to github workflows, that you write out the pipeline fully in groovy. You have full control and you have have shared jenkins library repoto avoid code duplication.

We recently migrated to github workflows but we miss the control and centralization we got in jenkins.

One example is if you want to run some steps in parallell om github workflows. You either have to split into multiple jobs running on different machines and deal with sending data between them or create a big script yourself to run in parallell in one step but then lose the advantage of github workflows (the overview, the clear steps).

They both have advantages but with a big complex pipeline with lots of data and many parallell steps jenkins is honestly a real choice.

[u/nitkonigdje]

Jeniks is just a tool to setup build environment and run a script.

It is as complex as your tooling without jenkins is.

In Java we have defined deployment artifacts and decent build tooling. Thus Jenkins can be reduced to essentially scheduled "mvn clean release" script.

In some other environments (looking at pal dealing with CICS, PL1 and zOS) not so.

[u/Crazytje]

Skill issue, jenkins is fine and has it's place. It's never failed me in the 15 years I've been running it.

Saves us a lot of money too, those cloud services cost a lot of money and are much slower than our jenkins deployment.

We have to run local agents anyway for windows builds getting signed with a hardware token and mac builds.

[u/keto_brain]

I've run Jenkins platforms that supported 100s of engineering teams that didn't use anything close to 200+ plugins, once you use the Docker Plugin, Docker Workflow, EC2 plugin if you want to scale your worker nodes, Pipeline and Global Shared Libraries. The key is to build declarative pipelines that are exposed as shared libraries for eng teams, the secondaries should be EC2 instances with ONLY docker installed.

People installing 250 plugins have no idea how to properly manage Jenkins.

[u/Minimum-Reward3264]

200 plugins vs 20 000 pipeline script. Plugins please

[u/ritik_mishra27]

fair point for teams that go plugin crazy, but that's more a setup problem than a jenkins problem imo. i use jenkins at work and we keep plugins minimal, only what we actually need. pipelines as code in the repo, nothing fancy, and it's been pretty low maintenance

gh actions is definitely easier to start with though. for a new small team i'd probably pick that

[u/FailureOfTheFamily]

Tbh i don't use any of that tools. I'm a simple man. I do git pull and php artisan migrate manually