Azure DevOps Pipeline Failure Triage Notes
Summarise a failed build and propose next checks.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Help me triage a failed Azure Pipelines run. Pipeline name and trigger: [PIPELINE]. Log excerpt around the failure (secrets removed): [LOG_EXCERPT]. What changed since the last green run: [RECENT_CHANGES]. Environment: [ENVIRONMENT]. Explain in plain words what the log says, expanding abbreviations on first use. List the three most likely causes with the evidence from the log for each, and a checklist of checks from quickest to slowest, changing one thing at a time. Say what would confirm or rule out each cause, how to tell a flaky test from a real regression over several runs, and what to record in the work item. Do not ask for or repeat secrets. If the excerpt lacks information, list the exact lines or variables to look at next. Warn me not to rerun a deployment stage blindly if the failure may have left a partial change. Finish with a team channel message under 80 words.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.