Feature/cd flow

[KerstenBreuer]

• adds a cd pipeline that upon every push to the dev (and eventually int) branch:
  • generates a version of the following pattern:
  • <last tag of branch>-<commit count since tag>-<short commit hash>-<branch>
  • if no tag was set yet it will use 0.0.0
  • example if the last tag was 0.5.2, there were 17 commits since that tag, and the last commit has the short hash 776c95c and the branch that triggered the CD was dev: 0.5.2-17-776c95c-dev
  • please note, the tags/releases but not these commit-based versions are following semantic versioning
  • a docker container is built and published to docker hub
  • the docker repo name is the same as the github repo name
  • the commit version generated before serves as image tag
  • update the deployment repo:
  • send a webhook to the github repository containing deployment helm charts
  • parameters are:
    • "chart_name": the name of this github repo
    • "new_version": commit version as generated above
  • the corresponding helm chart will be updated with the new commit version as the appVersion, the appVersion is used as docker image tag
• add a Dockerfile for deployment
• pin versions in the setup.py

I am looking forward to your suggestions :)

(The merge of this PR will trigger the CD workflow for the first time, so this will serve as initial test.)

[deepakunni3]

Thanks @KerstenBreuer for the well thought out flow for continuous delivery 👍

[KerstenBreuer]

Thanks @deepakunni3 :)

[KerstenBreuer]

Thanks, @ac-jorellanaf, I tested it on another repo, there it worked fine. However, there is unfortunately only one way how to test it on this repo and that is to merge it. So let's keep our fingers crossed. ;)

[KerstenBreuer]

@alamgirmani I hope that it's fine that I merge it now, so that we get this tested.