Lately I've being asked, since I'm known as a Jenkins expert, whether we're starting to see Jenkins' end-of-life. Since there are many CI-alternatives for Jenkins, and most of it are low-code alternatives (Yaml-based), while Jenkins is not introducing a yaml-based-CI alternative, it seems that this question is valid.
Still, the dominated-install-base of Jenkins, the large community, the fear-of-change (and the cost of it) and the fact that Jenkins is much more than a CI tool, the end-of-life for Jenkins is very far away. New projects, especially in new startups (that doesn't even know sometimes that Jenkins exists), usually pick other-than-Jenkins alternatives, and we'll face this fact more in the future.
But old projects will stick to Jenkins for a long time, so - for now - the answer to the topic-question 'Jenkins end-of-life' is probably 'no'. WDYT?