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

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

@macf00bar
I assume this is still looking at debugging Nuke rather than DevOps pipelines? I tend to remove the "don't deploy to dev from a feature branch" checks when adjusting pipelines, but you're right it doesn't feel good.
@zhaph yes, was talking about debugging nuke. I'm fine now how it works and I'm glad I can run and debug locally without having to commit, push, create PR, run pipeline and hope for the best.
What was really annoying was to have to decompile/step into nuke code to figure stuff out (esp. with regards to Azure DevOps...whoever created that piece of sh...instead of using what GitHub does...idk.)
Hm, maybe I will create a blog about it so nobody else has to get through it the same way I did.
GitHub - nektos/act: Run your GitHub Actions locally 🚀

Run your GitHub Actions locally 🚀. Contribute to nektos/act development by creating an account on GitHub.

GitHub
@khalidabuhakmeh too bad, I have the azure DevOps constraint (otherwise I've switched to GitHub Actions long time ago
@khalidabuhakmeh tbh, I have some sort of working solution with nuke, but honestly, it's on the same level as complicated as plain azure-devops-yaml

@macf00bar Looks like you might be able to run an agent locally to test against. That said... thoughts and prayers.

https://github.com/microsoft/azure-pipelines-agent/

GitHub - microsoft/azure-pipelines-agent: Azure Pipelines Agent 🚀

Azure Pipelines Agent 🚀. Contribute to microsoft/azure-pipelines-agent development by creating an account on GitHub.

GitHub
@khalidabuhakmeh thank deity, I have a local on premise docker build agent, otherwise I'd given up a week ago