triaging-pipelines
Triage recent Azure Pipelines runs and failures.
Datos de origen
- Repositorio
- dotnet/docker-tools
- Última actividad en el origen
- 20 de mayo de 2026 a las 21:29
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 181
- Forks
- 67
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- triaging-pipelines
- description
- Triage recent Azure Pipelines runs and failures.
## Workflow
### Step 1: List recent builds
```shell
pwsh ./eng/docker-tools/skill-helpers/Get-RecentBuilds.ps1 -Organization dnceng -Project internal -Folder dotnet/docker-tools -Hours 24
```
Change the value of `-Hours` to list more or fewer builds.
### Step 2: Investigate failures
For any build whose state is `failed`, `partiallySucceeded`, or `canceled`, use the `investigating-pipeline` skill to view the build timeline and read failing task logs.
### Step 3: Correlate failures with recent pull requests and issues
To check recent issues, run `gh issue list --state all`.
To check recent pull requests, run `gh pr list --state all`.
Read the contents of issues and pull requests using the `gh` CLI if necessary.
Look for:
- A recent change that obviously caused the failure
- An existing known issue tracking this failure
- An open pull request that already addresses the failure
Ver en GitHub