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.
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events