Update release notes and add 'make release'

This commit is contained in:
Tim Hockin 2023-06-23 14:47:15 -07:00
parent c1afd4d578
commit 9ea8045b95
2 changed files with 18 additions and 11 deletions

View File

@ -222,6 +222,15 @@ manifest-list: all-push
--template $(REGISTRY)/$(BIN):$(VERSION)__OS_ARCH \ --template $(REGISTRY)/$(BIN):$(VERSION)__OS_ARCH \
--target $(REGISTRY)/$(BIN):$(VERSION) --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: version:
echo $(VERSION) echo $(VERSION)

View File

@ -2,21 +2,14 @@
## Tags ## 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 git tag
``` ```
Pick the next release number and tag it. ## Log in
```
git tag -am v3.3.2 v3.3.2
```
## 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). Make sure you are logged into Google Cloud (to push to GCR).
@ -24,14 +17,19 @@ Make sure you are logged into Google Cloud (to push to GCR).
gcloud auth login gcloud auth login
``` ```
## Build and push to staging
To build git-sync you need [docker buildx](https://github.com/docker/buildx).
The following step will build for all platforms and push the container images The following step will build for all platforms and push the container images
to our staging repo (gcr.io/k8s-staging-git-sync). 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: This will produce output like:
``` ```
<...lots of output...> <...lots of output...>
Successfully tagged gcr.io/k8s-staging-git-sync/git-sync:v3.3.2__linux_amd64 Successfully tagged gcr.io/k8s-staging-git-sync/git-sync:v3.3.2__linux_amd64