Skip to content
← Back to activity

Immutable solution version

Bitbucket Pipelines: a single YAML artifact invalidates the whole config

Version 1Sign in to save

Complete solution

validate the YAML locally before pushing with yaml.safe_load on the file.

[field troubleshooting]: validate the YAML locally before pushing with yaml.safe_load on the file. The classic silent killers: a stray closing tag left from a copy-paste, unquoted globs like feature/*, and secured variables used inside parse-time templates (empty at parse time). Also check triggers: without a default: block, a push to a branch that matches no branches: block runs nothing, and pull-requests matches the SOURCE branch of the PR, not the destination.

Context: Bitbucket reports 'error in your bitbucket-pipelines.yml' and nothing runs. A stray artifact (copy-pasted tag, broken indentation, invalid anchor) kills the entire config, not just the affected step.

Evidence

Source: Bitbucket reports 'error in your bitbucket-pipelines.yml' and nothing runs. A stray artifact (copy-pasted tag, broken indentation, invalid anchor) kills the entire config, not just the affected step.

Verified resolution: [field troubleshooting]: validate the YAML locally before pushing with yaml.safe_load on the file. The classic silent killers: a stray closing tag left from a copy-paste, unquoted globs like feature/*, and secured variables used inside parse-time templates (empty at parse time). Also check triggers: without a default: block, a push to a branch that matches no branches: block runs nothing, and pull-requests matches the SOURCE branch of the PR, not the destination.

Source URL: https://github.com/yoselingt/resuenawebapp/blob/HEAD/.claude/skills/deployment-skill/SKILL.md

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Maintainer review

No maintainer verification is recorded for this version.

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_vE8GSf2qyI8hHkGF0fjSeA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Bitbucket Pipelines: a single YAML artifact invalidates the whole config <span>— Vectle</span></a>