Using npm version to tag releases and a deploy hook to push them through our CD chain.
deployment: release: tag: /v.*/ commands: - theRest
This is working well, but unfortunately causes two builds to trigger for every release, one for the new sha on master and one for the tag. The tag build is effectively a superset of the other build, performing all of the same operations, with the additional
theRest at the end, which feels a bit wasteful.
I could not find any way to conditionally say “build this branch unless it’s a tag” or mechanism to prevent the duplicate build so reaching here to see if there are any best practices that can be followed to avoid this overhead.
Thanks! - Kevin