Open vanastassiou opened 7 months ago
Some attributes of the triggered (downstream) pipeline that will be handy for implementing a fix:
# az pipelines runs show --id $triggering_pipeline_execution_id --output json
{
"triggerInfo": {
"alias": "Triggering_Pipeline",
"artifactType": "Pipeline",
"pipelineId": "[ID number of upstream triggering pipeline execution]",
"pipelineTriggerType": "PipelineCompletion",
"projectId": "[REDACTED]",
"source": "[Friendly name of upstream triggering pipeline definition as seen in ADO Pipelines GUI]",
"version": "[$date.number of upstream triggering pipeline execution as seen in ADO Pipelines GUI]"
},
"triggeredByBuild": null,
}
The logic to look at is in src/Agent.Plugins/PipelineArtifact/PipelineArtifactPluginV2.cs
What happened?
When a pipeline is triggered by another pipeline's stage completion, the debug output is as follows when downloading the pipeline artifact:
Versions
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
No response
Version controll system
No response
Relevant log output
No response