onos release job: tagging failed but jenkins job succeeded -- no artifacts published

onos release/tagging job:
 
https://jenkins.opencord.org/job/version-tag_wildcard/416/console
11:55:45 Version string '2.13-SNAPSHOT' in 'pom.xml' is not a SemVer released version, skipping.
11:55:46 Finished: SUCCESS

Version string problem identified in pom.xml.
Job reported success.

Release job success greets downstream problems with silence:

• Gerrit and github repositories were not tagged by the release.
• Artifacts were not published to nexus (staging) and maven central.

A lint check could detect this problem early.

This behavior (warn invalid then continue) may have been intended behavior.

Release involves running a few asynchronous tasks (should revisit this).
Failing midstream during a release job after partial tagging or incomplete artifact publishing may create ugly conditions for recovery.

Possible solutions:

• Perform release tasks twice, initially as a dry run to verify, then apply.
• Perform release with a fallback strategy
  • Deprecate or invalidate branches and artifacts
  • Publish artifacts as pre-release then apply for formal publishing (github release supports this).
  • Create a branch tag as *-pre or *-temp and rename to release after becoming reasonably sure the release job can succeed.