Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: describe the release process #82

Merged
merged 3 commits into from
Sep 15, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/release.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# kubectl-trace Release Process

Our release process is automated using [goreleaser](https://github.com/goreleaser/goreleaser).

When we release we do the following process:

1. We decide together (usually in the #kubectl-trace channel in Kubernetes slack) what's the next version to tag
2. A person with repository rights does the tag
3. The same person runs goreleaser in their machine
4. The tag is live on Github with the artifacts
5. Travis builds the tag and push the related docker images

## Release commands

Tag the version

```bash
git tag -a v0.1.0-rc.0 -m "v0.1.0-rc.0"
git push origin v0.1.0-rc.0
```

Run goreleaser, make sure to export your GitHub token first.

```
export GITHUB_TOKEN=<YOUR_GH_TOKEN>
make cross
```