Skip to content

Commit

Permalink
Update release notes and add 'make release'
Browse files Browse the repository at this point in the history
  • Loading branch information
thockin committed Jun 23, 2023
1 parent c1afd4d commit 9ea8045
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 10 deletions.
9 changes: 9 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -222,6 +222,15 @@ manifest-list: all-push
--template $(REGISTRY)/$(BIN):$(VERSION)__OS_ARCH \
--target $(REGISTRY)/$(BIN):$(VERSION)

release:
if [ -z "$(TAG)" ]; then \
echo "ERROR: TAG must be set"; \
false; \
fi
docker pull "$(BUILD_IMAGE)"
git tag -am "$(TAG)" "$(TAG)"
make manifest-list

version:
echo $(VERSION)

Expand Down
18 changes: 8 additions & 10 deletions RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,36 +2,34 @@

## Tags

First, see what has been tagged:
First, pick the new tag. Usually this means to see what has already been
tagged, and pick the next release number.

```
git tag
```

Pick the next release number and tag it.
## Log in

Make sure you are logged into Google Cloud (to push to GCR).

```
git tag -am v3.3.2 v3.3.2
gcloud auth login
```

## Build and push to staging

To build git-sync you need [docker buildx](https://github.com/docker/buildx).

Make sure you are logged into Google Cloud (to push to GCR).

```
gcloud auth login
```

The following step will build for all platforms and push the container images
to our staging repo (gcr.io/k8s-staging-git-sync).

```
make manifest-list
make release TAG="<tag you chose above>"
```

This will produce output like:

```
<...lots of output...>
Successfully tagged gcr.io/k8s-staging-git-sync/git-sync:v3.3.2__linux_amd64
Expand Down

0 comments on commit 9ea8045

Please sign in to comment.