... | ... | @@ -4,12 +4,12 @@ |
|
|
|
|
|
Assign as many issues as you can resolve up to the release date.
|
|
|
|
|
|
2. Create a [new issue](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=) with the title in format `Release YY.MM` - year, month, and optionally the index of the release within that month.
|
|
|
2. Create a [new issue](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/issues/new) with the title in format `Release YY.MM` - year, month, and optionally the index of the release within that month.
|
|
|
|
|
|
Copy the necessary steps of the following description into the new issue.
|
|
|
|
|
|
```markdown
|
|
|
Update Docker image tags of all KYPO microservices in the file [kypo-crp-deployment/provisioning/group_vars/all.yml](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/blob/master/provisioning/group_vars/all.yml).
|
|
|
Update Docker image tags of all KYPO microservices in the `values.yaml` appropriate charts of individual services [kypo-crp-helm/kypo-crp-head/charts](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/tree/master/helm/kypo-crp-head/charts). E.g. [adaptive-training](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-helm/-/blob/master/helm/kypo-crp-head/charts/adaptive-training/values.yaml).
|
|
|
* [ ] Java:
|
|
|
* [user-and-group](https://gitlab.ics.muni.cz/muni-kypo-crp/backend-java/kypo2-user-and-group)
|
|
|
* [training](https://gitlab.ics.muni.cz/muni-kypo-crp/backend-java/kypo2-training)
|
... | ... | @@ -21,6 +21,7 @@ |
|
|
* [ ] Python:
|
|
|
* [sandbox service](https://gitlab.ics.muni.cz/muni-kypo-crp/backend-python/kypo-sandbox-service)
|
|
|
* [ansible runner](https://gitlab.ics.muni.cz/muni-kypo-crp/backend-python/kypo-ansible-runner)
|
|
|
* [mitre technique](https://gitlab.ics.muni.cz/muni-kypo-crp/backend-python/kypo-mitre-technique-service)
|
|
|
* [ ] Angular:
|
|
|
* [trainings](https://gitlab.ics.muni.cz/muni-kypo-crp/frontend-angular/kypo2-trainings)
|
|
|
|
... | ... | @@ -33,25 +34,29 @@ |
|
|
|
|
|
Assign this issue to all group leaders and let them do the integration and testing using the local Vagrant/VirtualBox KYPO instance.
|
|
|
|
|
|
3. 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.
|
|
|
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`
|
|
|
|
|
|
1. If you have already deployed the release branch before and the branch has changed, rerun only the penultimate stage **plan-stage** and then continue with step 4. Otherwise, continue with step 2.
|
|
|
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.
|
|
|
|
|
|
2. Change the variable `kypo_crp_ansible_commit` 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/-/blob/master/tfvars/stage.tfvars) to the release branch.
|
|
|
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.
|
|
|
|
|
|
3. Check the Gitlab CI pipeline for the previous change and wait until all the stages up to the last are checked.
|
|
|
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.
|
|
|
|
|
|
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).
|
|
|
|
|
|
4. Check the Gitlab CI pipeline for the previous change and wait until all the stages up to the last are checked.
|
|
|
|
|
|
![image](uploads/20d9e942def4425826c4902a17a8f182/image.png)
|
|
|
|
|
|
4. 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 deployment Ansible provisioning.
|
|
|
|
|
|
![Screenshot_from_2021-06-03_17-57-35](uploads/ae6fbf543fe7bfc2cf0ad86b237af467/Screenshot_from_2021-06-03_17-57-35.png)
|
|
|
|
|
|
**Note**: Optionally you can select **redeploy-stage**, which will first destroy all related cloud resources, including KYPO Head, and start from scratch. Do not use this option too frequently. We have a limit on certificate generation.
|
|
|
|
|
|
5. Wait until the new version of the KYPO CRP instance is deployed.
|
|
|
6. Wait until the new version of the KYPO CRP instance is deployed.
|
|
|
|
|
|
4. Inform others about deployed KYPO instance on staging server. Send a message to the channel KYPOLAB in MS Teams:
|
|
|
5. Inform others about deployed KYPO instance on staging server. Send a message to the channel KYPOLAB in MS Teams:
|
|
|
|
|
|
```markdown
|
|
|
**KYPOLAB** na stránke **https://stage.crp.kypo.muni.cz** sa nachádza náhľad na release `YY.MM`. Prosím vás skontrolujte, že všetky zmeny, ktoré ste požadovali/nahlásili sú implementované, nasadné a fungujú podľa vašich predstáv.
|
... | ... | @@ -71,7 +76,7 @@ |
|
|
Pokiaľ sa prihlásite pomocou MUNI OIDC a chcete si nastaviť iné práva ako trainee, využite jedného z All Mighty users.
|
|
|
```
|
|
|
|
|
|
5. Go through the related [milestone](https://gitlab.ics.muni.cz/groups/muni-kypo-crp/-/milestones) and check if the issues are resolved in the deployed KYPO instance. If so, write the following comment.
|
|
|
6. Go through the related [milestone](https://gitlab.ics.muni.cz/groups/muni-kypo-crp/-/milestones) and check if the issues are resolved in the deployed KYPO instance. If so, write the following comment.
|
|
|
|
|
|
```markdown
|
|
|
Verified on staging instance of KYPO CRP release YY.MM.
|
... | ... | @@ -81,9 +86,9 @@ |
|
|
|
|
|
And close the issue. If not, report the issue to the responsible group leader and go back to the previous step.
|
|
|
|
|
|
6. Check if the documentation is up to date.
|
|
|
7. Check if the documentation is up to date.
|
|
|
|
|
|
7. Once everything is ready to be released, create release tags in format `YY.MM` from tags previously specified in the file [kypo-crp-deployment/provisioning/group_vars/all.yml](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/blob/master/provisioning/group_vars/all.yml) and again update the file with release tags.
|
|
|
8. Once everything is ready to be released, create release tags in format `YY.MM` from tags previously specified in the file [kypo-crp-deployment/provisioning/group_vars/all.yml](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/blob/master/provisioning/group_vars/all.yml) and again update the file with release tags.
|
|
|
|
|
|
* Java:
|
|
|
* [user-and-group](https://gitlab.ics.muni.cz/muni-kypo-crp/backend-java/kypo-user-and-group/-/tags/new)
|
... | ... | @@ -119,7 +124,7 @@ |
|
|
* Issue one.
|
|
|
```
|
|
|
|
|
|
8. Finally, merge the release issue and create a release tag on the [deployment project](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/tags/new) in the same format as the others `YY.MM`.
|
|
|
9. Finally, merge the release issue and create a release tag on the [deployment project](https://gitlab.ics.muni.cz/muni-kypo-crp/devops/kypo-crp-deployment/-/tags/new) in the same format as the others `YY.MM`.
|
|
|
|
|
|
Compose release notes from all previous components and optionally from the deployment project.
|
|
|
|
... | ... | @@ -139,7 +144,7 @@ |
|
|
* Issue one.
|
|
|
```
|
|
|
|
|
|
9. Inform others about a new release of KYPO CRP. Send a message to the channel KYPOLAB in MS Teams:
|
|
|
10. Inform others about a new release of KYPO CRP. Send a message to the channel KYPOLAB in MS Teams:
|
|
|
|
|
|
```markdown
|
|
|
**KYPOLAB** všetko potrebné je otagované.
|
... | ... | @@ -153,4 +158,4 @@ |
|
|
...
|
|
|
```
|
|
|
|
|
|
10. Contact Martin Horák who will create a tweet that we have released a new version of the KYPO CRP. Provide him a release notes mainly the list of new features and their usage. |
|
|
\ No newline at end of file |
|
|
11. Contact Martin Horák who will create a tweet that we have released a new version of the KYPO CRP. Provide him a release notes mainly the list of new features and their usage. |
|
|
\ No newline at end of file |