From 43ebec9c9298aba63ca49bd1d3521014e31454fe Mon Sep 17 00:00:00 2001 From: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com> Date: Mon, 16 Jan 2023 14:19:32 +0000 Subject: [PATCH] :book: remove the workaround steps from the release doc ## Description remove the workaround steps from the release doc. these steps are from the legacy method, which is no longer used --- RELEASE.md | 24 +----------------------- 1 file changed, 1 insertion(+), 23 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 3c130a888b2..25912d01afb 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -50,28 +50,6 @@ For more info, see the release page: https://github.com/kubernetes-sigs/kubebuil 2. Announce the new release via email is sent to `kubebuilder@googlegroups.com` with the subject `[ANNOUNCE] Kubebuilder $VERSION is released` -## What to do if things goes wrong? How to release from my local env as a workaround? - -As a workaround we can release from locally by: - -PS.: _This workaround uses the google cloud. Note that we move the binary CLI release from google cloud to use Github Actions instead_ - -1. Download google container builder: https://github.com/GoogleCloudPlatform/cloud-build-local -2. Verify that you can use the cloud-build-local CLI tool -3. Ensure that you are locally in the branch created for the release (`release-`) -4. Ensure that it has no changes in the code source ( `git status`) -5. Create the directory `cloudbuild` (`mkdir cloudbuild`) -6. Then, update the file `build/cloudbuild_local.yaml` with: - -The following change is required for Goreleaser be able to add the binaries in the release page. - -```sh -env: ["SNAPSHOT=1","GITHUB_TOKEN=your github token with access in the repo"] -``` -**NOTE** You can create a token [here](https://github.com/settings/tokens/new). - -7. Then, update the file `build/build_kubebuilder.sh` to remove the flag `--snapshot` (Otherwise, the binaries will be built with snapshot git commit hash instead of the tag version) -8. Run the command to trigger the release `$ cloud-build-local --config=build/cloudbuild_local.yaml --dryrun=false --write-workspace=./cloudbuild .` ## HEAD releases @@ -141,4 +119,4 @@ However, the image should still be built and maintained since other projects und [kubebuilder-release-tools]: https://github.com/kubernetes-sigs/kubebuilder-release-tools [release-notes-generation]: https://github.com/kubernetes-sigs/kubebuilder-release-tools/blob/master/README.md#release-notes-generation -[release-process]: https://github.com/kubernetes-sigs/kubebuilder/blob/master/VERSIONING.md#releasing \ No newline at end of file +[release-process]: https://github.com/kubernetes-sigs/kubebuilder/blob/master/VERSIONING.md#releasing