mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

14K
active users

#azuredevops

2 posts2 participants0 posts today

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

If you have #git repos in #AzureDevOps with multiple main branches that PRs are created for, create a ".azuredevops/pull_request_targets.yml" file. This will help it pick the proper target branch for your PRs, instead of always using the default branch.

learn.microsoft.com/en-us/azur

Microsoft Learn
learn.microsoft.comConfigure custom target branches for pull requests - Azure ReposLearn how to specify a list of branches as potential pull request targets.