Post

Ben Reader | 🔌😈

@powers-hell.com

A friendly reminder that variable syntax in #AzureDevOps isn't important until it is. Which is all the time. Refresh your knowledge today so you don't end up like *someone* I know who was fixing a pipeline template bug at 1 am... It's me, hi! I'm the idiot, it's me... #DevOps #MVPBuzz #PowerShell

learn.microsoft.comDefine variables - Azure PipelinesVariables are name-value pairs defined by you for use in a pipeline. You can use variables as inputs to tasks and in your scripts.

21/8/25, 10:58 am0 reposts4 likes

@leodarcy.bsky.social

Yeah, been there and feel your pain 😭 Hope it all worked out 🤞

Ben Reader | 🔌😈

@powers-hell.com

Yeah it was fine, I was just sitting there wondering what on earth was causing half my tasks to not compile... Didn't use expression variables.. what an idiot!

Ben Reader | 🔌😈

@powers-hell.com

Also, whilst troubleshooting complex pipeline templates that compile differently based on variable / parameter values, never forget that the "Download full YAML" option exists. It performs the "compile" step for you, allowing you to debug without actually committing changes or running the pipeline.

Ben Reader | 🔌😈

@powers-hell.com

This is actually just a standard REST call that you can make and can be done in any terminal / VSCode instance as long as you know how to form the request URI

Ben Reader | 🔌😈

@powers-hell.com

For those who don't like clicking links - expression variables ${{ variables.var }} process at compile, BEFORE runtime - macro syntax $(var) process at runtime BEFORE tasks - runtime expressions $[variables.var] also process at runtime BEFORE tasks but are meant for conditional expressions.