Currently, the checks for whether to publish or not in Jenkins is
looking for the branch name for a commit to be "main", and then there's
a check for git description --tags returning a perfect semver tag.
This check is broken, since pushes with tagged versions will have
a branch name being the version tag (e.g. v1.2.0), rather than
having a branch name of main.
The fix is to check for the branch name being a version tag (i.e. a
v followed by a semver version number, e.g. v1.2.0). This check
is added to the Jenkinsfile, so we can eliminate any conditionals/checking of
branches/tags in bin/publish (i.e. that script publishes
unconditionally).
Currently, the checks for whether to publish or not in Jenkins is looking for the branch name for a commit to be "main", and then there's a check for
git description --tagsreturning a perfect semver tag.This check is broken, since pushes with tagged versions will have a branch name being the version tag (e.g.
v1.2.0), rather than having a branch name ofmain.The fix is to check for the branch name being a version tag (i.e. a
vfollowed by a semver version number, e.g.v1.2.0). This check is added to the Jenkinsfile, so we can eliminate any conditionals/checking of branches/tags inbin/publish(i.e. that script publishes unconditionally).