Bitbucket Pipelines: OIDC token silently empty without oidc true

TL;DR

Related silent gotchas: a pipeline where the first step is trigger manual never starts on push, a bulk push of more than 5 new refs triggers zero pipelines, the pipeline config API 404s until Pipelines has been enabled on the repo at least once, and secured vars used in parse-time templates resolve empty. The OIDC token is only populated when the step opts in with oidc: true; without it the variable exists but is empty and auth fails downstream.

Fix

1. Related silent gotchas: a pipeline where the first step is trigger manual never starts on push, a bulk push of more than 5 new refs triggers zero pipelines, the pipeline config API 404s until Pipelines has been enabled on the repo at least once, and secured vars used in parse-time templates resolve empty. Expected: You get the expected result; the problem is gone.

When to use

• You are setting up or using this Bitbucket Pipelines feature.
• The symptom matches: OIDC token silently empty without oidc true.

When NOT to use

• Unrelated Bitbucket Pipelines issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Bitbucket Pipelines. Source: https://github.com/jenyapoyarkov/bb-pipelines-author-skill/blob/HEAD/skills/bb-pipelines-author-skill/SKILL.md.

Variant phrasings

OIDC token silently empty without oidc true

Why it happens

OIDC-based deploys fail: the BITBUCKETSTEPOIDC_TOKEN variable is silently empty.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/jenyapoyarkov/bb-pipelines-author-skill/blob/HEAD/skills/bb-pipelines-author-skill/SKILL.md

Source: OIDC-based deploys fail: the BITBUCKETSTEPOIDC_TOKEN variable is silently empty.

Verified resolution: [field troubleshooting]: the OIDC token is only populated when the step opts in with oidc: true; without it the variable exists but is empty and auth fails downstream. Related silent gotchas: a pipeline where the first step is trigger manual never starts on push, a bulk push of more than 5 new refs triggers zero pipelines, the pipeline config API 404s until Pipelines has been enabled on the repo at least once, and secured vars used in parse-time templates resolve empty. Cache miss every run usually means key.files does not match the actual lockfile name.

Source URL: https://github.com/jenyapoyarkov/bb-pipelines-author-skill/blob/HEAD/skills/bb-pipelines-author-skill/SKILL.md