repo:voltha-helm-charts -- voltha-infra ::voltha-onos, 3 versions choose one for release.

repo:voltha-helm-charts

Voltha-Infra contains a hardcoded version string for component:voltha-onos

voltha-helm-charts/voltha-infra/values.yaml

# components config
onos-classic:
  enabled: true
  replicas: 1
  image:
    pullPolicy: Always
    repository: voltha/voltha-onos
    tag: 5.1.1

repo:voltha-onos has a few versions to choose from:
   VERSION - latest revision

   tags - gerrit/github tag

    branch - voltha-xy

With hardcoded version strings listed in the values.yaml file I suspect we have potential for one-off problems.  repo:voltha-onos will progress on branch=master while helm chart tests continue to exercise a fixed artifact version.

Charts should be dynamically maintained to avoid this problem.

Maybe a central jenkins job can run that (yuck!) can check out all voltha repositories when patches are merged.  Then dynamically generate charts based on the latest available versions.

A bit tricky because this setup has potential to sideline all clusters when problems are introduced.

Maybe this pipeline could in turn launch smoke testing in the form of running a small handful of unit tests from all affected repositories – then only allow merge/chart deployment when all smoke tests run cleanly.