Merge pull request #3157 from camilamacedo86/clean-release-info

🌱 : cleanup info and code regards legacy actions using GCP to build KB CLI release
kubernetes-sigs · Jan 16, 2023 · 26f605e · 26f605e
2 parents 9f8c026 + 74ecc86
commit 26f605e
Show file tree

Hide file tree

Showing 5 changed files with 2 additions and 238 deletions.
diff --git a/RELEASE.md b/RELEASE.md
@@ -86,13 +86,8 @@ The releases occur in an account in the Google Cloud (See [here](https://console
 
 ### To build the Kubebuilder CLI binaries:
 
-A trigger `build-kb-release` is configured to call [build/cloudbuild.yaml](build/cloudbuild.yaml).
-This trigger will be executed when any new tag be published. 
-The tags must be built from the release branch (Currently, `release-3`).
-
-Also, we have a trigger to generate snapshots builds from the master branch.
-This trigger will call [build/cloudbuild_snapshot.yaml](build/cloudbuild_snapshot.yaml)
-when any change needs to be performed on master.
+A trigger GitHub action [release](.github/workflows/release.yml) is trigged when a new tag is pushed.
+This action will caall the job [./build/.goreleaser.yml](./build/.goreleaser.yml).
 
 ### To build the Kubebuilder-tools: (Artifacts required to use ENV TEST)
 

diff --git a/build/build_kubebuilder.sh b/build/build_kubebuilder.sh
diff --git a/build/cloudbuild.yaml b/build/cloudbuild.yaml
diff --git a/build/cloudbuild_local.yaml b/build/cloudbuild_local.yaml
diff --git a/build/cloudbuild_snapshot.yaml b/build/cloudbuild_snapshot.yaml