LEGO's Philosophy on Builds vs. Jenkins' Reality
Description
The image is a screenshot of a tweet from user Eva Ferreira (@evaferreira92). Her tweet says, 'Did you hear that, Jenkins?!' and is a reply to a quoted tweet from the official LEGO Group account (@LEGO_Group). The LEGO tweet reads, 'I don't know who needs to hear this but there is no such thing as a bad build.' The humor is a classic pun based on the double meaning of the word 'build.' For LEGO, a 'build' is a physical creation with their toy bricks, where creativity is paramount and there are no mistakes. For a software developer, a 'build' is the automated process of compiling code into a usable artifact, a process managed by tools like Jenkins. These software builds can, and frequently do, fail or become 'bad' or 'broken,' halting development. The joke is a sarcastic, relatable jab at the notorious fragility of CI/CD pipelines, personifying Jenkins as a tool that needs to hear LEGO's forgiving philosophy
Comments
8Comment deleted
The difference is that when a LEGO build is bad, you just have a weird-looking spaceship. When a Jenkins build is bad, you have a weird-looking spaceship on fire, in production, at 3 AM
LEGO says there’s no bad build - Jenkins heard that, updated 487 plugins at once, and turned the pipeline into an avant-garde red/green art installation
LEGO's marketing team accidentally wrote the most optimistic Jenkins pipeline documentation ever - clearly they've never experienced the joy of a build that passes locally but fails in CI because someone's test depends on the system clock being set to Pacific Time
LEGO's inspirational message about builds hits different when you've spent 3 hours debugging why Jenkins decided that today, specifically today, your previously green build should fail with 'Error: Success' - a contradiction that somehow feels perfectly on-brand for a tool that's been the backbone of CI/CD since before Docker made everything 'easier.' The real irony? LEGO instructions are deterministic and reproducible, while Jenkins builds are more like Schrödinger's pipeline: simultaneously passing and failing until you check the logs, at which point they're definitely failing, but for reasons that disappeared when you re-ran it
LEGO says there’s no such thing as a bad build; Jenkins replies with an “unstable” badge, exit code 137, and a mysteriously green check after the third retry
LEGO: “no bad builds”; Jenkins: tell that to my red ball from a flaky E2E, a 429 from the artifact repo, and an expired credentialsId in stage("Deploy")
Jenkins to LEGO: 'Challenge accepted - watch this monorepo merge turn prod red at 5 PM Friday.'
bruh Comment deleted