Azure / Azure/azure-cli-extensions

AZ pipelines build list command does not show triggerInfo field data on manual triggered deployment job.

Open
#4,446 11 comments 1 reaction 0 assignees View on GitHub
customer-reported DevOps Pipelines Service Attention
Dominant language
Python
Stars
454
Forks
1.7k
Avg merge
2d 19h
Merged PRs (30d)
64

Description

- If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at [Azure/azure-cli](https://github.com/Azure/azure-cli/issues)

### 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)

When executing 'az pipelines build list' command against a YAML pipeline (deployment job yaml pipeline), the result returns with triggerInfo field populated with the resources consumed by this build by some but not all builds. What's the reason for this? I inspected 2 of the entries returned: Both are have 'reason' field as 'manual' but only 1 has 'triggerInfo' field populated

Example:

reason : manual
... (omit for security)
.. (omit for security)
status : completed
tags : {}
triggerInfo : @{alias=ProcessApi-accesscontrol-resource; artifactType=Pipeline; pipelineId=26091; pipelineTriggerType=PipelineCompletion; projectId=***;
source=ProcessApi-AccessControlService; version=AccessControlService_0.0.20220125.1}

reason : manual
.. (omit for security)
.. (omit for security)
triggerInfo :

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.