2021-04-07 12:39:16 +02:00
---
2022-03-25 11:08:17 +01:00
sort: 18
2021-04-07 12:39:16 +02:00
---
# Release process guidance
2019-12-02 22:00:11 +01:00
2022-08-31 01:27:24 +02:00
## Prereqs
1. Make sure you have enterprise remote configured
```
git remote add enterprise < url >
```
2. Make sure you have singing key configured
3. Make sure you have github token with at least `read:org, repo, write:packages` permissions exported under `GITHUB_TOKEN` env variable.
You can create token [here ](https://github.com/settings/tokens )
2019-12-02 22:00:11 +01:00
## Release version and Docker images
2019-11-30 19:36:10 +01:00
2022-04-06 10:41:09 +02:00
0. Make sure that the release commits have no security issues.
2022-07-29 23:15:49 +02:00
1a. Document all the changes for new release in [CHANGELOG.md ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/docs/CHANGELOG.md ).
2022-08-31 01:27:24 +02:00
1b. Add `(available starting from v1.xx.y)` line to feature docs introduced in the upcoming release.
2022-04-04 11:14:27 +02:00
2. Create the following release tags:
2022-01-31 18:18:48 +01:00
* `git tag -s v1.xx.y` in `master` branch
* `git tag -s v1.xx.y-cluster` in `cluster` branch
* `git tag -s v1.xx.y-enterprise` in `enterprise` branch
* `git tag -s v1.xx.y-enterprise-cluster` in `enterprise-cluster` branch
2022-08-31 01:27:24 +02:00
3. Run `TAG=v1.xx.y make publish-release` . This command performs the following tasks:
a) Build and package binaries in `*.tar.gz` release archives with the corresponding `_checksums.txt` files inside `bin` directory.
This step can be run manually with the command `make release` from the needed git tag.
b) Build and publish [multi-platform Docker images ](https://docs.docker.com/build/buildx/multiplatform-images/ )
for the given `TAG` , `TAG-cluster` , `TAG-enterprise` and `TAG-enterprise-cluster` .
The multi-platform Docker image is built for the following platforms:
* linux/amd64
* linux/arm64
* linux/arm
* linux/ppc64le
* linux/386
This step can be run manually with the command `make publish` from the needed git tag.
2022-09-08 13:51:17 +02:00
4. Push the tags created `v1.xx.y` and `v1.xx.y-cluster` at step 2 to public GitHub repository at https://github.com/VictoriaMetrics/VictoriaMetrics .
**Important note:** do not push enteprise tags to public GitHub repository - they must be pushed only to private repository.
5. Run `TAG=v1.xx.yy make github-create-release github-upload-assets` . This command performs the following tasks:
a) Create draft GitHub release with the name `TAG` . This step can be run manually
2022-08-31 01:27:24 +02:00
with the command `TAG=v1.xx.y make github-create-release` .
The release id is stored at `/tmp/vm-github-release` file.
2022-09-08 13:51:17 +02:00
b) Upload all the binaries and checksums created at step `3a` to that release.
2022-08-31 01:27:24 +02:00
This step can be run manually with the command `make github-upload-assets` .
It is expected that the needed release id is stored at `/tmp/vm-github-release` file,
2022-09-08 13:51:17 +02:00
which must be created at the step `a` .
2022-08-31 01:27:24 +02:00
If the upload process is interrupted by any reason, then the following recovery steps must be performed:
- To delete the created draft release by running the command `make github-delete-release` .
This command expects that the id of the release to delete is located at `/tmp/vm-github-release`
2022-09-08 13:51:17 +02:00
file created at the step `a` .
2022-08-31 01:27:24 +02:00
- To run the command `TAG=v1.xx.y make github-create-release github-upload-assets` , so new release is created
and all the needed assets are re-uploaded to it.
2022-09-08 13:51:17 +02:00
6. Go to < https: // github . com / VictoriaMetrics / VictoriaMetrics / releases > and verify that draft release with the name `TAG` has been created
2022-08-31 01:27:24 +02:00
and this release contains all the needed binaries and checksums.
2022-09-08 13:51:17 +02:00
7. Update the release description with the [CHANGELOG ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/docs/CHANGELOG.md ) for this release.
8. Remove the `draft` checkbox for the `TAG` release and manually publish it.
9. Bump version of the VictoriaMetrics cluster in the [sandbox environment ](https://github.com/VictoriaMetrics/ops/blob/main/sandbox/manifests/benchmark-vm/vmcluster.yaml )
2022-08-31 01:27:24 +02:00
by [opening and merging PR ](https://github.com/VictoriaMetrics/ops/pull/58 ).
2019-11-30 19:36:10 +01:00
2022-03-22 12:40:55 +01:00
## Building snap package
2020-12-29 10:43:09 +01:00
2022-03-22 12:40:55 +01:00
pre-requirements:
* snapcraft binary, can be installed with commands:
2020-12-29 10:43:09 +01:00
for MacOS `brew install snapcraft` and [install mutipass ](https://discourse.ubuntu.com/t/installing-multipass-on-macos/8329 ),
for Ubuntu - `sudo snap install snapcraft --classic`
2022-03-22 12:40:55 +01:00
* exported snapcraft login to `~/.snap/login.json` with `snapcraft export-login login.json && mkdir -p ~/.snap && mv login.json ~/.snap/`
* already created release at github (it operates `git describe` version, so git tag must be annotated).
2020-12-29 10:43:09 +01:00
2022-04-04 11:14:27 +02:00
1. checkout to the latest git tag for single-node version.
2. execute `make release-snap` - it must build and upload snap package.
3. promote release to current, if needed manually at release page [snapcraft-releases ](https://snapcraft.io/victoriametrics/releases )
2020-12-29 10:43:09 +01:00
2022-03-22 12:40:55 +01:00
### Public Announcement
2020-12-19 20:58:03 +01:00
2022-03-22 12:40:55 +01:00
* Publish message in Slack at < https: // victoriametrics . slack . com >
* Post at Twitter at < https: // twitter . com / MetricsVictoria >
* Post in Reddit at < https: // www . reddit . com / r / VictoriaMetrics />
* Post in Linkedin at < https: // www . linkedin . com / company / victoriametrics />
* Publish message in Telegram at < https: // t . me / VictoriaMetrics_en > and < https: // t . me / VictoriaMetrics_ru1 >
* Publish message in google groups at < https: // groups . google . com / forum /#! forum / victorametrics-users >
2019-11-30 19:36:10 +01:00
## Helm Charts
The helm chart repository [https://github.com/VictoriaMetrics/helm-charts/ ](https://github.com/VictoriaMetrics/helm-charts/ )
2022-03-22 12:40:55 +01:00
### Bump the version of images
2019-11-30 19:36:10 +01:00
2022-04-04 11:14:27 +02:00
1. Update `vmagent` chart version in [`values.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-agent/values.yaml ) and [`Chart.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-agent/Chart.yaml )
2. Update `vmalert` chart version in [`values.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-alert/values.yaml ) and [`Chart.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-alert/Chart.yaml )
3. Update `vmauth` chart version in [`values.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-auth/values.yaml ) and [`Chart.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-auth/Chart.yaml )
4. Update `cluster` chart versions in [`values.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-cluster/values.yaml ), bump version for `vmselect` , `vminsert` and `vmstorage` and [`Chart.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-cluster/Chart.yaml )
5. Update `k8s-stack` chart versions in [`values.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/values.yaml ), bump version for `vmselect` , `vminsert` , `vmstorage` , `vmsingle` , `vmalert` , `vmagent` and [`Chart.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/Chart.yaml )
2022-05-09 14:27:38 +02:00
6. Update `single-node` chart version in [`values.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-single/values.yaml ) and [`Chart.yaml` ](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-single/Chart.yaml )
2022-04-04 11:14:27 +02:00
8. Run `make gen-doc`
9. Run `make package` that creates or updates zip file with the packed chart
10. Run `make merge` . It creates or updates metadata for charts in index.yaml
11. Push changes to master. `master` is a source of truth
12. Push the changes to `gh-pages` branch
2019-11-30 19:36:10 +01:00
2022-04-04 11:14:27 +02:00
## Ansible Roles
2022-03-22 12:40:55 +01:00
2022-04-04 11:14:27 +02:00
### Bump the version of images
2019-11-30 20:08:48 +01:00
2022-04-04 11:14:27 +02:00
Repository [https://github.com/VictoriaMetrics/ansible-playbooks ](https://github.com/VictoriaMetrics/ansible-playbooks )
2019-11-30 20:08:48 +01:00
2022-04-04 11:14:27 +02:00
1. Update `vmagent` version in [`main.yml` ](https://github.com/VictoriaMetrics/ansible-playbooks/blob/master/roles/vmagent/defaults/main.yml#L4 )
2. Update `vmalert` version in [`main.yml` ](https://github.com/VictoriaMetrics/ansible-playbooks/blob/master/roles/vmalert/defaults/main.yml#L4 )
3. Update `cluster` version in [`main.yml` ](https://github.com/VictoriaMetrics/ansible-playbooks/blob/master/roles/cluster/defaults/main.yml#L3 )
4. Update `single` version in [`main.yml` ](https://github.com/VictoriaMetrics/ansible-playbooks/blob/master/roles/single/defaults/main.yml#L6 )
5. Commit changes
6. Create a new tag
7. Create a new release. This automatically publishes the new versions to galaxy.ansible.com