Instead of overriding with kubernate commands in elixir-omg CI, it nows triggers job in helm-development repo to start the deployment.
For master updates, it will trigger an update to helm-development using git sha as the app_version and change the dev env version as well. This would end up having the CircleCI jobs inside helm-development to deploy it.
For release tags changes, it will trigger an update to helm-development using semver as the app_version (same as before)
Changes
add increase_chart_version_XXX jobs for master and release
remove old deployment script and jobs
remove childchain deployment job to omg-childchain-v1 repo
:clipboard: https://github.com/omgnetwork/devops/issues/407
need helm repo PR changes: https://github.com/omgnetwork/helm-development/pull/470 childchain component in : https://github.com/omgnetwork/omg-childchain-v1/pull/15
Overview
Instead of overriding with kubernate commands in elixir-omg CI, it nows triggers job in helm-development repo to start the deployment.
helm-development
using git sha as theapp_version
and change the dev env version as well. This would end up having the CircleCI jobs insidehelm-development
to deploy it.helm-development
using semver as theapp_version
(same as before)Changes
increase_chart_version_XXX
jobs for master and releaseTesting
used the playground repos: https://github.com/omgnetwork/elixir-omg-boolafish-playground, https://github.com/omgnetwork/helm-development-boolafish-playground