To be fair to nuke though, I got it to work now, I can only debug it with VsCode but not with Visual Studio, but that's a minor glitch.

I think, with what I have now I can move on and create even more complex builds.

#nukebuild #buildautomation #ci #azuredevops #csharp #dotnet

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

@khalidabuhakmeh I knew it, only because @nuke added support for it recently https://github.com/nuke-build/nuke/pull/1024 #NukeBuild

Is there an easy built-in way of capturing #NukeBuild Tool output as a string?

Of course, I could just iterate over the output and build the string, but I was hoping for something built-in, as I though that's a pretty common task.