如何在VSTS中列出发布过程中使用的全部变量（含变量组）？

Great question! I totally get the frustration of not having a single consolidated view for all variables—including those from variable groups, release-level variables, environment-specific variables, and even historical runs. Octopus Deploy’s unified variable view is definitely a high bar to reference, so let’s go through some practical workarounds for Azure DevOps:

1. Use the Azure DevOps REST API to Aggregate Variables #

The native UI doesn’t combine all these variable sources, but the REST API lets you pull data from multiple endpoints and stitch it together. Here’s how to approach it:

• Fetch the release definition: Call the release definitions API to get both direct variables and linked variable groups:

  GET https://dev.azure.com/{your-org}/{your-project}/_apis/release/definitions/{definition-id}?api-version=7.1-preview.4
  

  This returns a variables object (direct release/environment variables) and a variableGroups array (IDs of linked groups).
• Fetch variable group details: For each variable group ID from the previous step, call the variable groups API to get its variables:

  GET https://dev.azure.com/{your-org}/{your-project}/_apis/distributedtask/variablegroups/{group-id}?api-version=7.1-preview.2
  

• Include historical release variables: To get variables used in past runs, call the releases API for specific release IDs:

  GET https://dev.azure.com/{your-org}/{your-project}/_apis/release/releases/{release-id}?api-version=7.1-preview.8
  

  This includes environment-specific variables that might have been overridden during the run.

You can write a quick PowerShell or Python script to combine all this data into a single table or JSON output—this gives you a full, unified list of every variable used (or ever used) in your release pipeline.

2. Try Third-Party Extensions from the Azure DevOps Marketplace #

There are several community-built extensions that solve this exact problem by aggregating variables across sources:

• Look for extensions like Variable Inspector or Release Variable Exporter—many of these let you view all variables (including variable groups) in one place, and some even support exporting to CSV for offline review.
• Always check user reviews and update history to pick a reliable, maintained extension.

3. Build a Custom Power BI Report (For Long-Term Visibility) #

If you need a persistent, shareable view, connect Power BI to your Azure DevOps project using the Azure DevOps data connector. You can:

• Pull data from release definitions, variable groups, and release history tables.
• Create a custom report that shows all variables, their sources, and where they’ve been used in historical runs.
• Share this report with your team via the Azure DevOps dashboard or Power BI service.

Note on Native Support #

As of now, Azure DevOps doesn’t have a native unified variable view like Octopus Deploy. If this is a critical feature for your team, head over to the Azure DevOps Feedback Forum to submit a feature request and vote for existing ones—this helps prioritize the feature for the product team.

内容的提问来源于stack exchange，提问作者Lassi Autio