Skip to content

Commit

Permalink
docs: describe the release process (#82)
Browse files Browse the repository at this point in the history
docs: describe the release process

Co-authored-by: Leo Di Donato <[email protected]>
  • Loading branch information
leodido authored Sep 15, 2019
2 parents 544f59d + 64577fa commit f1af597
Showing 1 changed file with 28 additions and 0 deletions.
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
```

0 comments on commit f1af597

Please sign in to comment.