<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Is Jenkins Dead? No, And That's Much Worse</title><link>https://devopstoolkit.live/bedtime/is-jenkins-dead-no-and-thats-much-worse/index.html</link><description>Gather round. Get comfortable, kids. Tonight, I’m going to read you a bedtime story.
This is the tale of Jenkins. The butler who never once said no.
Now, this is not one of those stories where the hero loses. Jenkins won. Jenkins won everything. For the better part of a decade, if you wrote software for a living, Jenkins stood between your keyboard and your customers, and it built your code, and it tested it, and it shipped it, every single night, without ever once being thanked.
And here’s the thing.
Almost nobody chooses Jenkins any more. Ask around your office and you will find people who would rip it out tomorrow morning. They can’t. Twenty-odd years after a young engineer at Sun Microsystems wrote the first version of it, it is still there, still running the thing that actually ships your product, and everybody has quietly agreed not to fucking touch it.
So tuck in. Because tonight’s nightmare isn’t that our hero dies at the end. It’s that he doesn’t. He is still running tonight. And you cannot switch him off.</description><generator>Hugo</generator><language>en-us</language><lastBuildDate/><atom:link href="https://devopstoolkit.live/bedtime/is-jenkins-dead-no-and-thats-much-worse/index.xml" rel="self" type="application/rss+xml"/></channel></rss>