Skip to content

Commit

Permalink
Update release and build info in docs
Browse files Browse the repository at this point in the history
  • Loading branch information
okushchenko committed Oct 11, 2017
1 parent 86418a9 commit c7e0da1
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 10 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Go 1.8 is required to build confd, which uses the new vendor directory.
$ mkdir -p $GOPATH/src/github.com/kelseyhightower
$ git clone https://github.com/kelseyhightower/confd.git $GOPATH/src/github.com/kelseyhightower/confd
$ cd $GOPATH/src/github.com/kelseyhightower/confd
$ ./build
$ make
```

You should now have confd in your `bin/` directory:
Expand Down
13 changes: 4 additions & 9 deletions docs/release-checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,14 +24,9 @@ This script will generate all merged changes since $LATEST_RELEASE and append it

You'll need to manually modify "HEAD" to show up as the latest release.

When drafting a new release, you must make sure that a `darwin` and `linux` build of confd have
been uploaded. If you have cross-compile support, you can use the following command to generate
those binaries:

$ CONFD_CROSSPLATFORMS="darwin/amd64 linux/amd64" NEW_RELEASE="x.y.z"
$ for platform in $CONFD_CROSSPLATFORMS; do \
GOOS=${platform%/*} GOARCH=${platform##*/} ./build; \
mv bin/confd bin/confd-$NEW_RELEASE-${platform%/*}-${platform##*/}; \
done
When drafting a new release, you must make sure that a `darwin`, `linux` and `windows` build of confd have
been uploaded. You must have Docker installed to build release binaries:

$ make release

You can then drag and drop these binaries into the release draft.

0 comments on commit c7e0da1

Please sign in to comment.