Skip to content

Changes

Page history
Update Release checklist authored by Dominik Pilár's avatar Dominik Pilár
Hide whitespace changes
Inline Side-by-side
Release-checklist.md
View page @ ae678834
......@@ -34,21 +34,26 @@
Assign this issue to all group leaders and let them do the integration and testing using the local Vagrant/VirtualBox KYPO instance.
3. Increase the `version` in [kypo-crp-head](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/blob/master/helm/kypo-crp-head/Chart.yaml) chart file. Version should be created as a release candidate. E.g. `0.0.1-rc.1`
3. Increase the `version` of the [kypo-crp-head](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/blob/master/helm/kypo-crp-head/Chart.yaml) chart with a **release candidate** suffix, e.g., if the latest version is `0.0.4` change it to `0.0.5-rc.1`. Don't forget to update the `appVersion`.
4. Once the release branch is ready to be merged, deploy the KYPO instance on the staging server and check whether the KYPO CRP works properly.
1. If you have already deployed the release branch before and you want to update the microservice/s, update the required tag/s in [stage.yaml](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/value-files/stage.yaml). Furthermore, if the configuration of [kypo-crp-helm](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm) has been changed, increase its version in [chart file](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/blob/master/helm/kypo-crp-head/Chart.yaml) and reflect this version to `kypo_crp_head_version` in [stage.tfvars](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/tfvars/stage.tfvars) then continue with step 4. Otherwise, continue with step 2.
1. **A)** If you deploy the release branch for the first time, don't skip any step.
**B)** If you have already deployed the release branch before and:
* you have changed only the tag/s of microservice/s, skip step 2.
* you have changed only configuration files of the [kypo-crp-head](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/tree/master/helm/kypo-crp-head) chart in [kypo-crp-helm](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm) project, skip step 3.
* you have changed tag/s and configuration files, don't skip any steps.
2. Change the variable `kypo_crp_head_version` in the file [muni-kypo-tf-kypo-crp/tfvars/stage.tfvars](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/tfvars/stage.tfvars) to the release branch.
2. Make sure that you have set the **kypo-crp-head** chart version properly with release candidate suffix. Whenever you are changing the configuration files of **kypo-crp-head** chart (except the image tags) increase only the release candidate version. Then set the variable `kypo_crp_head_version` in the file [muni-kypo-tf-kypo-crp/tfvars/stage.tfvars](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/tfvars/stage.tfvars) to be the same as in the release branch.
3. Update the versions of microservices in [stage.yaml](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/value-files/stage.yaml) to match the versions specified in appropriate charts of [kypo-crp-helm](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/tree/master/helm/kypo-crp-head/charts).
3. Make sure that all versions of [microservices charts](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/tree/master/helm/kypo-crp-head/charts) are updated and propagated to the [stage.yaml](https://gitlab.ics.muni.cz/muni-kypo/deployment/terraform/muni-kypo-tf-kypo-crp-kubernetes/-/blob/master/value-files/stage.yaml) file.
4. Check the Gitlab CI pipeline for the previous change and wait until all the stages up to the last are checked.
![image](uploads/9d3321ce3eb1813a94993cb353750163/image.png)
5. Jobs of the last stage are manual. Click on the gear icon and select **apply-stage** to run deployment Ansible provisioning.
5. Jobs of the last stage are manual. Click on the gear icon and select **apply-stage** to run Helm deployment.
![Screenshot_from_2022-06-01](uploads/4d41e0899de140ec729e9c377de90a42/Screenshot_from_2022-06-01.png)
......