Skip to content

Commit 63c2636

Browse files
Merge pull request #8344 from MicrosoftDocs/users/jukullam/ai-tip
Add guidance for using AI to identify variable syntax issues
2 parents 7f086e1 + 243510d commit 63c2636

File tree

2 files changed

+54
-0
lines changed

2 files changed

+54
-0
lines changed

docs/pipelines/process/runs.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ ms.custom: devx-track-azurecli, ai-assisted
66
ms.assetid: 0d207cb2-fcef-49f8-b2bf-ddb4fcf5c47a
77
ms.date: 06/09/2025
88
monikerRange: "<=azure-devops"
9+
ms.collection:
10+
- ce-skilling-ai-copilot
911
---
1012

1113
# Pipeline runs
@@ -223,6 +225,40 @@ Delete a tag from a pipeline run in your project using the [az pipelines runs ta
223225
```azurecli
224226
az pipelines runs tag delete --run-id 123 --tag YAML
225227
```
228+
## Manage runs with the Azure DevOps MCP Server
229+
230+
You can manage pipeline runs in Copilot with the Azure DevOps MCP server. To get started, see [Enable AI assistance with Azure DevOps MCP Server](../../mcp-server/mcp-server-overview.md).
231+
232+
### List pipeline runs
233+
234+
List the pipeline runs for a particular pipeline.
235+
236+
```copilot-prompt
237+
Show the three most recent runs for the Tailspin pipeline.
238+
```
239+
240+
This prompt lists the last three pipeline runs with a link to view each run.
241+
242+
### Show pipeline run details
243+
244+
Fetch the status of a specific build.
245+
246+
```copilot-prompt
247+
Show the status and details for build 12345678.9.
248+
```
249+
250+
This prompt returns returns the status, result, start/finish time, and summary for a build.
251+
252+
### Start a new pipeline run
253+
254+
Begin a new run of a pipeline.
255+
256+
```copilot-prompt
257+
Start the Tailspin pipeline and provide a direct link to the run, including the project name in the URL.
258+
```
259+
260+
This prompt starts your pipeline and and provides a link to the pipeline run.
261+
226262

227263
::: moniker-end
228264

docs/pipelines/process/variables.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ ms.topic: conceptual
66
ms.assetid: 4751564b-aa99-41a0-97e9-3ef0c0fce32a
77
ms.date: 10/03/2024
88
ai-usage: ai-assisted
9+
ms.collection:
10+
- ce-skilling-ai-copilot
911
---
1012

1113
# Define variables
@@ -149,6 +151,22 @@ Choose a runtime expression if you're working with [conditions](conditions.md) a
149151

150152
Typically a template variable is the standard to use. By leveraging template variables, your pipeline will fully inject the variable value into your pipeline at pipeline compilation. This is helpful when attempting to debug pipelines. You can download the log files and evaluate the fully expanded value that is being substituted in. Since the variable is substituted in, you shouldn't leverage template syntax for sensitive values.
151153

154+
### Use AI to identify variable syntax issues
155+
156+
This is an example prompt for Copilot Chat that identifies what types of variables are used in a pipeline and when the variables will resolve. Highlight your YAML code and then enter the following Copilot Chat prompt.
157+
158+
```copilot-prompt
159+
What types of Azure DevOps variables are used in this YAML pipeline? Give specific examples.
160+
When does each variable process in the pipeline?
161+
How will each variable render when not found?
162+
What stages and jobs will the variables be available for?
163+
```
164+
165+
Customize your prompt to add specifics as needed.
166+
167+
> [!TIP]
168+
> Copilot is powered by AI, so surprises and mistakes are possible. For more information, see [Copilot FAQs](https://aka.ms/copilot-general-use-faqs).
169+
152170
## Set variables in pipeline
153171

154172
#### [YAML](#tab/yaml/)

0 commit comments

Comments
 (0)