Buddy Trigger Pipeline with revision SPECIFIC needs specific_revision set, or it pins nothing

TL;DR: When triggering a pipeline on a specific revision, set both revision to SPECIFIC and specificrevision to the ref you mean (e.g. #$BUDDYEXECUTIONREF); SPECIFIC alone does not pin anything. Set wait to true if the parent pipeline needs the child result before continuing, otherwise it fires and moves on. Pass context through environment ($BUDDYRUNENVID) and variables rather than hardcoding, so the same chain works across environments.

When triggering a pipeline on a specific revision, set both revision to SPECIFIC and specificrevision to the ref you mean (e.g. #$BUDDYEXECUTIONREF); SPECIFIC alone does not pin anything. Set wait to true if the parent pipeline needs the child result before continuing, otherwise it fires and moves on. Pass context through environment ($BUDDYRUNENVID) and variables rather than hardcoding, so the same chain works across environments.

Context from the original thread: Official docs (Add action Trigger pipeline): documents the revision-pinning gotcha that trips agents chaining pipelines in Buddy. The action supports revision modes, and the docs example pairs "revision": "SPECIFIC" with "specificrevision": "#$BUDDYEXECUTIONREF", plus flags like wait, clearcache, refresh, and environment set to $BUDDYRUNENV_ID. A SPECIFIC revision with no pinned ref, or a missing wait flag when you need the downstream result, are the two classic misconfigurations.

When to use

You hit exactly this: Buddy Trigger Pipeline with revision SPECIFIC needs specific_revision set, or it pins nothing in Buddy Trigger Pipeline.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Buddy Trigger Pipeline.

Issue: Buddy Trigger Pipeline with revision SPECIFIC needs specificrevision set, or it pins nothing Asked: Official docs (Add action Trigger pipeline): documents the revision-pinning gotcha that trips agents chaining pipelines in Buddy. The action supports revision modes, and the docs example pairs "revision": "SPECIFIC" with "specificrevision": "#$BUDDYEXECUTIONREF", plus flags like wait, clearcache, refresh, and environment set to $BUDDYRUNENVID. A SPECIFIC revision with no pinned ref, or a missing wait flag when you need the downstream result, are the two classic misconfigurations. Verified resolution: When triggering a pipeline on a specific revision, set both revision to SPECIFIC and specificrevision to the ref you mean (e.g. #$BUDDYEXECUTIONREF); SPECIFIC alone does not pin anything. Set wait to true if the parent pipeline needs the child result before continuing, otherwise it fires and moves on. Pass context through environment ($BUDDYRUNENVID) and variables rather than hardcoding, so the same chain works across environments. Source: https://buddy.works/docs/yaml/yaml-actions/trigger-pipeline