Background: To ensure that an example service doesn't depend on a feature in the hzn CLI or horizon agent that the user doesn't have installed yet, exchangePublish.sh currently checks the version that hzn version returns, adds v at the beginning, and clones the examples repo and switches to that branch (if it exists). These branches have to be manually created, so it is error prone.
Solution:
[x] (bruce) Modify exchangePublish.sh to use a tag instead of a branch
[x] (ben) Modify the devops pipeline such that when it creates the weekly release and tag in the anax repo, it creates the same tag in the examples repo (e.g. v2.29.0-558)
bmpotter
commented
3 years ago
Background: To ensure that an example service doesn't depend on a feature in the
hznCLI or horizon agent that the user doesn't have installed yet,exchangePublish.shcurrently checks the version thathzn versionreturns, addsvat the beginning, and clones theexamplesrepo and switches to that branch (if it exists). These branches have to be manually created, so it is error prone.Solution:
exchangePublish.shto use a tag instead of a branchanaxrepo, it creates the same tag in theexamplesrepo (e.g.v2.29.0-558)