Nixpkgs version Stable (25.05) Steps to reproduce The fetchFromRepoOrCz function in pkgs/build-support/fetchrepoorcz/default.nix downloads sources from https://repo.or.cz/ Unfortunately, the site b...
Welcome back to "Bricks and Builds with Chay," where the bricks are plenty, the builds are bold, and the banter is... well, let's just say it's uniquely Chay. Today, we're diving headfirst into the LEGO Star Wars 40755 Imperial Dropship vs. Rebel Scout Speeder set. Buckle up, folks—this one's
Just to be on record:
I honestly didn’t expect that even non-YAML code (👀 @nuke build – yeah, I’m talking to you...) would require just as many fucking never-ending commits.
Azure DevOps has proven me wrong. (lol)
The real pain point?
No local test run
No Run pipeline locally
Zero feedback until you PR, merge, and let it rip on main
So yeah, we’re basically testing on the main branch. In production. In 2025.
For everything else, there’s: ¯\_(ツ)_/¯
Also, I firmly believe that not only Carthage must be destroyed, but also:
- CI/CD with no local feedback loop
- “Works on my machine” excuses
_ YAML files that silently break on pasted tabs
- And every doc that starts with “just”
And yes — I really thought nuke build would make things better...
But after 24 hours of commits, checks, and trial-and-error, I’ve been proven otherwise (and I really wanted to make it work and local debugging is awesome — but it’s useless when the docs are a soggy mess and don’t reflect reality.)
#DevOps #AzureDevOps #YAML #NukeBuild #CI #CICD #MainBranchDrivenDevelopment
#WorksOnMyMachine #AgileStruggles #ModernDev #CarthagoDelendaEst #DevHumor
#BuildFail #DebuggingHell #LocalIsNotProd #SoftwareEngineering #DotNet #DevLife