Pipeline that requires other pipeline

yukipastelcat

I want to configure two pipelines - one runs npm package tests on every commit (default), other one publishes it to registry when commit is tagged with a version (tag pipeline). How can I ensure that tag pipeline executes only when default pipeline executed successfully? Is there anything like GitHub Actions jobs.<job_id>.needs?

Eddie Webbinaro

Not as such.

Is defining the npm package step as a reusable definition (YAML Anchor) sufficient? That way it is consistent, and would occur on each commit AND before publishing on a tag.  The package step can define the output as an `artifact` and pass it to the publish step.

https://support.atlassian.com/bitbucket-cloud/docs/yaml-anchors/