New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let's review and optimize activiti-cloud-acceptance-scenarios release pipeline #2273

Closed
igdianov opened this Issue Dec 14, 2018 · 2 comments

Comments

4 participants
@igdianov
Copy link
Member

igdianov commented Dec 14, 2018

so, that we only release activiti-cloud-example-chart when it passes all acceptance tests with aggregated activiti-cloud-application-chart, activiti-cloud-infrastructure-chart, activiti-cloud-modeler-chart, etc versions

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 mvn command.

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.

@ryandawsonuk

This comment has been minimized.

Copy link
Member

ryandawsonuk commented Dec 14, 2018

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.

@igdianov

This comment has been minimized.

Copy link
Member

igdianov commented Dec 14, 2018

We can also push good chart versions into final consumer charts repo as well as make promote to deploy latest version into production environment in the same or another cluster if needed

@salaboy salaboy added this to Open in Activiti 7.x via automation Dec 14, 2018

@salaboy salaboy added this to the RC1 milestone Dec 14, 2018

Activiti 7.x automation moved this from Open to Closed Dec 17, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment