File tree Expand file tree Collapse file tree 2 files changed +17
-10
lines changed
Expand file tree Collapse file tree 2 files changed +17
-10
lines changed Original file line number Diff line number Diff line change @@ -222,6 +222,15 @@ manifest-list: all-push
222222 --template $(REGISTRY ) /$(BIN ) :$(VERSION ) __OS_ARCH \
223223 --target $(REGISTRY ) /$(BIN ) :$(VERSION )
224224
225+ release :
226+ if [ -z " $( TAG) " ]; then \
227+ echo " ERROR: TAG must be set" ; \
228+ false ; \
229+ fi
230+ docker pull " $( BUILD_IMAGE) "
231+ git tag -am " $( TAG) " " $( TAG) "
232+ make manifest-list
233+
225234version :
226235 echo $(VERSION )
227236
Original file line number Diff line number Diff line change 22
33## Tags
44
5- First, see what has been tagged:
5+ First, pick the new tag. Usually this means to see what has already been
6+ tagged, and pick the next release number.
67
78```
89git tag
910```
1011
11- Pick the next release number and tag it.
12+ ## Log in
13+
14+ Make sure you are logged into Google Cloud (to push to GCR).
1215
1316```
14- git tag -am v3.3.2 v3.3.2
17+ gcloud auth login
1518```
1619
1720## Build and push to staging
1821
1922To build git-sync you need [ docker buildx] ( https://github.com/docker/buildx ) .
2023
21- Make sure you are logged into Google Cloud (to push to GCR).
22-
23- ```
24- gcloud auth login
25- ```
26-
2724The following step will build for all platforms and push the container images
2825to our staging repo (gcr.io/k8s-staging-git-sync).
2926
3027```
31- make manifest-list
28+ make release TAG="<tag you chose above>"
3229```
3330
3431This will produce output like:
32+
3533```
3634<...lots of output...>
3735Successfully tagged gcr.io/k8s-staging-git-sync/git-sync:v3.3.2__linux_amd64
You can’t perform that action at this time.
0 commit comments