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

[hb66772-home]

• If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

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 :

[ghost]

Thank you for your feedback. This has been routed to the support team for assistance.

[yonzhan]

route to CXP team

[navba-MSFT]

@hb66772-home Apologies for the late reply. Could you please let me know if you face the same issue by using most recent version of the Az CLI ? Awaiting your reply.

[hb66772-home]

Can you specify which version Of CLI that will provide this capability?

On Wed, Feb 23, 2022 at 11:46 PM navba-MSFT @.***> wrote:

@hb66772-home https://github.com/hb66772-home Apologies for the late reply. Could you please let me know if you face the same issue by using most recent version https://docs.microsoft.com/en-us/cli/azure/install-azure-cli of the Az CLI ? Awaiting your reply.

— Reply to this email directly, view it on GitHub https://github.com/Azure/azure-cli-extensions/issues/4446#issuecomment-1049515659, or unsubscribe https://github.com/notifications/unsubscribe-auth/APICVN52SX4SBBPGEVBHNXDU4XA2NANCNFSM5O7UCMGA . You are receiving this because you were mentioned.Message ID: @.***>

[navba-MSFT]

@hb66772-home Thanks for getting back. Could you check with recent version AzCLI 2.33.1 and let us know if you still see the issue? Awaiting your reply.

[hb66772-home]

I've downloaded/installed 2.33.1 and executed below command PS C:> az version { "azure-cli": "2.33.1", "azure-cli-core": "2.33.1", "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" } }

But again, the trigger info is not shown and i still could not find the consumed artifacts by this YAML deployment job pipeline (when it's manually invoked)

az pipelines build show --project $project --org $org --id $id

When the pipeline is 'automatically triggered' by a build completion event, then the trigger info is populated as seen below

Below is how the deployment job includes the pipeline resource as 'pipeline resource' in the yaml

Note:

1. I notice that this command only show triggerInfo IF AND ONLY IF the deployment job was triggered a buildcompletion event from the pipeline resource that i included in the yaml deployment job.

2. If the deployment job yaml pipeline is triggered/invoke manually, the triggerInfo is empty and there is no way for me to pull the 'consumed artifacts' information from the result.

So, the ask/question if the consumed artifacts should always be included regardless of trigger type? or is it only shown only for all but manual trigger? or is this just a bug?

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @narula0781, @ashishonce, @romil07.

Issue Details

---

- 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 :

Author:	hb66772-home
Assignees:	navba-MSFT
Labels:	`customer-reported`, `Service Attention`, `Pipelines`, `DevOps`
Milestone:	-

[navba-MSFT]

@hb66772-home We have involved the Service Team in the background to look into this issue and update this github thread. We appreciate your patience on this.

[maxstepanov]

@navba-MSFT hi, any updates on this?

[pgangula-79]

Does anyone know if this is resolved or not? I still get no "triggerInfo.version" value for manually triggered builds.