search

weaveworks / weave-gitops-clusters

Configuration for the staging k8s clusters used by weave-gitops.
1 stars 1 forks source link

[Spike] Investigate WGE release process and pipelines #101

Closed katya-makarevich closed 2 years ago

katya-makarevich commented 2 years ago

Investigate:

Timebox: 4 hours max

MohamedMSaeed commented 2 years ago

add one more doc to investigate: https://www.notion.so/weaveworks/a1aefd60231d4f2d96cae5e1c3a0267a?v=c3e66fd2e77844e591f43b1a424b3d58

AhmedSa-mir commented 2 years ago

Investigation

The best way to support regression testing would be to add a new job/step in weave-enterprise acceptance-testing CI pipeline to update the release version after installing the WGE instance and running the tests afterthat. We believe that this task is out of our team's scope for 2 reasons: 1- It's not a global engineering issue that we need to handle. 2- The current pipeline is structured in a mix of scripts and CI jobs that creates a new cluster, installs WGE instance and runs the acceptance tests. For us to understand why it's structured like this and where should we add the update-release step can take a bunch of days of communication with Pesto team, while it could be implemented easily in a couple of hours or so by someone from Pesto team because they are familiar with their CI workflow.

From our side, we can add a script to update the release version of WGE instances installed by our provisioning tool so that engineers can test the upgrade process manually.