Variable reference is not valid. ':' was not followed by a valid variable name character. Consider using ${} to delimit the name

How to fix Azure DevOps “Variable reference is not valid. ‘:’ was not followed by a valid variable name character. Consider using ${} to delimit the name”

This article explains one possible reason why you might run into an error like “Variable reference is not valid. ‘:’ was not followed by a valid variable name character. Consider using ${} to delimit the name” when using a PowerShell task in an Azure DevOps pipeline. But hey – at…Continue reading How to fix Azure DevOps “Variable reference is not valid. ‘:’ was not followed by a valid variable name character. Consider using ${} to delimit the name”

bash - it's even more of a mystery than PowerShell

Azure DevOps fails with “Error: The path ‘/home/vsts/work/1/s/your-repo’ does not exist” even though the repository is there for sure?

Eh, this was a weird one. This article explains how to get around an issue where your build tools fail due to weird “path does not exist” errors when you’re using bash to execute a restore to your project. The build would probably succeed nicely, but it fails due to…Continue reading Azure DevOps fails with “Error: The path ‘/home/vsts/work/1/s/your-repo’ does not exist” even though the repository is there for sure?