Skip to content

Latest commit

 

History

History
47 lines (34 loc) · 2.46 KB

RELEASE.md

File metadata and controls

47 lines (34 loc) · 2.46 KB
Raw

TiChi Release Process

Overview

TiChi uses goreleaser to release in GitHub Actions, where the task compiles and packages the binary images.

Release Steps

  • Normal Release

    1. Fetch the latest code for upstream: git fetch upstream
    2. Create tag: git tag v1.5.12
    3. Push tag to upstream: git push upstream --tags
    4. Triggering GitHub Actions for releasing

  • Release exception, need to re-release

    1. Delete local code tag: git tag -d v1.5.12
    2. Delete upstream tag: git push --delete upstream v1.5.12
    3. Delete GitHub release drafts (if any)
    4. Fix the issue and re-run the normal releasing process

Deployment Steps

We use scripts to automate deployment and upgrades. When a pull request for bump version is merged, we use a prow job to run the script to complete the automatic deployment.

These tasks are defined in the following prow jobs:

In addition, for the test-infra components, we use a bot for the automatic bump, also defined in prow jobs:

Note

When we bump test-infra components we need to check ANNOUNCEMENTS.md to see if the update has Breaking Changes, and we need to test the development environment and see how the cluster is running before upgrading the prod environment.