We’re setting up automated deployment pipelines for our Aras 12.0 requirement management module using Azure DevOps. I’ve defined a YAML variable in our pipeline template that should expand to the target environment URL, but it’s not working as expected.
The variable is defined at the pipeline level:
variables:
targetEnv: $(Environment.URL)
deployPath: /InnovatorServer/Deploy
When the pipeline runs, the variable shows as literal text $(Environment.URL) instead of expanding to the actual value. I’ve tried both $() and ${{ }} syntax but getting different behaviors. The ${{ }} syntax throws a template expression error during pipeline validation.
This is blocking our automated deployment process since we can’t dynamically target different Aras environments. Has anyone dealt with YAML variable scoping issues in Azure DevOps pipelines for Aras deployments? I’m not sure if this is a template usage problem or syntax issue.
I’ve seen this exact issue with Aras deployment pipelines. The problem is usually that $(Environment.URL) is trying to reference a variable that doesn’t exist at that scope. In Azure DevOps, you need to pass variables explicitly to templates. If you’re using a template file, the parent pipeline must pass the variable as a parameter. Also, for Aras-specific deployments, make sure you’re not trying to expand variables inside script blocks that run in different contexts. The YAML parser and the script runtime have different variable resolution mechanisms.
The $() syntax is for runtime variables while ${{ }} is for compile-time template expressions. If Environment.URL is a pipeline variable or variable group, you need runtime syntax. However, template expressions evaluate before the pipeline runs, which is why you’re getting that error. Check if your variable is defined in the right scope - pipeline variables vs template parameters have different expansion rules.
Another thing to watch - if you’re using $() syntax inside a script task, the variable needs to be explicitly mapped to the script environment. Azure DevOps doesn’t automatically pass all pipeline variables to script contexts. You need to either use env: mapping in the task or access via $env:VARIABLE_NAME (PowerShell) or $VARIABLE_NAME (Bash). For Aras deployment scripts that connect to Innovator Server, this is critical because connection strings often use these dynamic variables.
Quick clarification - are you defining this in a template file or the main pipeline YAML? Template parameters use ${{ }} and must be passed from the parent pipeline. Runtime variables use $() but only work within the same file scope unless explicitly passed. For Aras deployments, I typically define environment URLs as variable groups in Azure DevOps library, then reference them with $(variableGroupName.URL) syntax. This keeps environment configs separate from pipeline code and works across template boundaries.