Open hb66772-home opened 2 years ago
Thank you for your feedback. This has been routed to the support team for assistance.
route to CXP team
@hb66772-home Apologies for the late reply. Thanks for sharing this feedback. We will look into this ask and provide an update here once we have more details on this.
@hb66772-home This is a quick update we have involved the Service team in the background to look into this ask and update this thread. We appreciate your patience on this.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @narula0781, @ashishonce, @romil07.
Author: | hb66772-home |
---|---|
Assignees: | navba-MSFT |
Labels: | `customer-reported`, `Service Attention`, `Pipelines`, `DevOps`, `CXP Attention` |
Milestone: | - |
Extension name (the extension in question)
{ "azure-cli": "2.25.0", "azure-cli-core": "2.25.0", "azure-cli-telemetry": "1.0.6", "extensions": { "application-insights": "0.1.13", "automation": "0.1.0", "azure-devops": "0.18.0", "front-door": "1.0.14", "storage-preview": "0.7.4" } }
Description of issue (in as much detail as possible)
requirements:
Problem:
Querying 'deployment center' in the log using 'az webapp deployment log' returns information of the yaml pipeline (deployment job yaml) which contains the build number of the deployment pipeline.
However, when querying Azure Devops using 'az pipelines build list' command and filtering it based on a build definition id, the list of build results returned showed some has triggerInfo populated and some don't.
Expectation: