Skip to content

Commit ad88531

Browse files
committed
Add guidance for using AI to identify variable syntax issues in YAML pipelines
1 parent 7f086e1 commit ad88531

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/pipelines/process/variables.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -149,6 +149,22 @@ Choose a runtime expression if you're working with [conditions](conditions.md) a
149149

150150
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.
151151

152+
### Use AI to identify variable syntax issues
153+
154+
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.
155+
156+
```copilot-prompt
157+
What types of Azure DevOps variables are used in this YAML pipeline? Give specific examples.
158+
When does each variable process in the pipeline?
159+
How will each variable render when not found?
160+
What stages and jobs will the variables be available for?
161+
```
162+
163+
Customize your prompt to add specifics as needed.
164+
165+
> [!TIP]
166+
> Copilot is powered by AI, so surprises and mistakes are possible. For more information, see [Copilot FAQs](https://aka.ms/copilot-general-use-faqs).
167+
152168
## Set variables in pipeline
153169

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

0 commit comments

Comments
 (0)