*: Remove cloudbuilder from the repository part 1 (#10433)

Signed-off-by: timflannagan <[email protected]>

.github/workflows/pr-unit-tests.yaml

@@ -1,29 +1,21 @@
 name: Unit Tests
 
-# This workflow invokes unit tests for the Gloo Gateway project
-# It was introduced during the 1.17 quarter, where we added a new project (projects/gateway2)
-# and therefore we only run those new tests here
-#
-# Our historical unit tests are run via CloudBuild
-# Overtime, it would be valuable to consolidate these approaches
-env:
-  VERSION: '1.0.0-ci1'
-  GITHUB_TOKEN: ${{ github.token }}
-
 on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review]
   merge_group:
     types: [checks_requested]
 
+env:
+  VERSION: '1.0.0-ci1'
+  GITHUB_TOKEN: ${{ github.token }}
+
 jobs:
   # Runs the unit tests for `projects/gateway2`
   kube_gateway_project:
     name: projects/gateway2
     runs-on: ubuntu-22.04
     timeout-minutes: 10
-    # Other unit tests are run by our CloudBuild runner
-    # These tests do run on Draft PRs, and so we maintain that consistency and run this job on Draft PRs as well
     steps:
     - uses: actions/checkout@v4
     - name: Setup Go

.gitignore

@@ -16,19 +16,13 @@ docker-local
 themes
 install/gloo.yaml
 
-cloudbuild-local*.yaml
-
 # OSX files
 .DS_Store
 docs/helm-values.md
 
 # ignore intermediate files that gomock sometimes generates
 **/gomock_reflect*
 
-## START Temporary exclusion while master/v0.20.x branch is supported
-old_docs_temp_dir/
-
-## END Temporary exclusion while master/v0.20.x branch is supported
 .vscode/launch.json
 .vscode/settings.json
 *__debug_bin

Makefile

@@ -230,11 +230,6 @@ run-e2e-tests: TEST_PKG = ./test/e2e/ ## Run all in-memory E2E tests
 run-e2e-tests: GINKGO_FLAGS += --label-filter="end-to-end && !performance"
 run-e2e-tests: test
 
-.PHONY: run-hashicorp-e2e-tests
-run-hashicorp-e2e-tests: TEST_PKG = ./test/consulvaulte2e/
-run-hashicorp-e2e-tests: GINKGO_FLAGS += --label-filter="end-to-end && !performance"
-run-hashicorp-e2e-tests: test
-
 .PHONY: run-kube-e2e-tests
 run-kube-e2e-tests: TEST_PKG = ./test/kube2e/$(KUBE2E_TESTS) ## Run the legacy Kubernetes E2E Tests in the {KUBE2E_TESTS} package
 run-kube-e2e-tests: test

ci/README.md

@@ -1,7 +1,6 @@
 # Continuous Integration
 - [Pull Request](#pull-request)
     - [Changelog Bot](#changelog-bot)
-    - [Build Bot](#build-bot)
     - [Github Actions](#github-actions)
     - [Bulldozer](#bulldozer)
     - [Special Labels](#special-labels)
@@ -14,21 +13,11 @@
 
 This is enabled as a GitHub App on the project, and if changes are required, please contact the maintainers of the project by [opening an issue](/devel/contributing/issues.md).
 
-### Build Bot
-[Build Bot](https://github.com/solo-io/build-bot) runs unit tests for the entire project. 
-
-This is enabled as a Github App on the project, and is configured by the [cloudbuild.yaml](../cloudbuild.yaml) at the root of the project and contains additional configuration in the [cloudbuild](cloudbuild) folder.
-
 ### Github Actions
 [Github Workflows](/.github/workflows) run tests which rely on Kubernetes clusters.
 
 See the [GitHub docs](https://docs.github.com/en/actions/automating-builds-and-tests/about-continuous-integration#about-continuous-integration-using-github-actions) for more deatils about how GitHub Actions work.
 
-### Bulldozer
-[Bulldozer](https://github.com/solo-io/bulldozer) automatically merges PRs when all required status checks are successful and required reviews are provided.
-
-This is enabled as a GitHub App on the project, and if changes are required, please contact the maintainers of the project by [opening an issue](/devel/contributing/issues.md).
-
 ### Special Labels
 **Keep PR Updated**: When applied, bulldozer keeps the PR up to date with the base branch, by merging any updates into it (Applied by default).
 
@@ -45,7 +34,6 @@ This is enabled as a GitHub App on the project, and if changes are required, ple
 
 **Skip Kubernetes E2E Tests**: Include `skipCI-kube-tests:true` in the changelog entry of the PR.
 
-
 ### Assets and Package Management
 `glooctl` is built and published to the GitHub release via the script `upload_github_release_assets.go`. This is sensitive to changes to the output of `glooctl version`.