Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Let's review and optimize activiti-cloud-acceptance-scenarios release pipeline #2273
so, that we only release
It will be much more efficient to run the tests within the change to the full example chart rather than testing the change to the chart outside within an updatebot pr in the acceptance tests...
To make it work, we need to make install current chart version into preview namespace, git clone latest activiti-cloud-acceptance-scenarios repo inside pipeline workspace and run acceptance tests with
If tests pass, we automatically merge PR and run release pipeline to build and release Helm chart in Github repository.
We can also automate publishing aggregated chart version into consumer chart repository in activiti-cloud-charts.
Remember we have activiti-cloud-example-chart which is a repo and we also have activiti-cloud-full-example inside activiti-cloud-charts that is used by external consumers.
I think it is OK to update activiti-cloud-example-chart ahead of scenarios running (as we currently do) but not propagate that to activiti-cloud-charts until the scenarios tests pass. So activiti-cloud-charts remains the repo for public consumers but is a consumer from acceptance-scenarios. The change then would be to propagate with updatebot the versions being applied within activiti-cloud-example-chart to activiti-cloud-full-example in activiti-cloud-charts at the end of the activiti-cloud-acceptance-scenarios pipeline. Or copy the whole chart over by cloning both repos and copying it.