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?
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/
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.