Today, service teams frequently encounter failures in the SDK validation pipeline, but the current experience makes it difficult for them to understand and resolve issues independently. This results in repeated escalations to the SDK team and slows down overall delivery.
Problem
Several gaps in the current pipeline experience are preventing effective self-service:
TSV Error Categorization is unclear: https://github.com/Azure/azure-rest-api-specs/actions/runs/25071193957/job/73451644463
Errors are not grouped or labeled in a meaningful way so people struggle to identify the root cause or required action.
Breaking Changes are not shown clearly
https://github.com/Azure/azure-rest-api-specs/pull/43781/checks?check_run_id=79743389395
The list of breaking changes is not visible in the ADO summary page.
Users must manually dig through logs to find relevant information.
SDK Generation Failure Summary is not actionable
https://github.com/Azure/azure-rest-api-specs/pull/43682/checks?check_run_id=79465703121
Failure summaries is clear and logs are verbose but not structured for quick diagnosis.
All of the above are blockers for enabling service team self-serve troubleshooting pipeline issues.
Today, service teams frequently encounter failures in the SDK validation pipeline, but the current experience makes it difficult for them to understand and resolve issues independently. This results in repeated escalations to the SDK team and slows down overall delivery.
Problem
Several gaps in the current pipeline experience are preventing effective self-service:
TSV Error Categorization is unclear: https://github.com/Azure/azure-rest-api-specs/actions/runs/25071193957/job/73451644463
Errors are not grouped or labeled in a meaningful way so people struggle to identify the root cause or required action.
Breaking Changes are not shown clearly
https://github.com/Azure/azure-rest-api-specs/pull/43781/checks?check_run_id=79743389395
The list of breaking changes is not visible in the ADO summary page.
Users must manually dig through logs to find relevant information.
SDK Generation Failure Summary is not actionable
https://github.com/Azure/azure-rest-api-specs/pull/43682/checks?check_run_id=79465703121
Failure summaries is clear and logs are verbose but not structured for quick diagnosis.
All of the above are blockers for enabling service team self-serve troubleshooting pipeline issues.