Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Esun Kim	1ce1159a75	[CI] Moved to Bazel 7 (#36105 ) Let's use Bazel 7 by default. Closes #36105 PiperOrigin-RevId: 617653203	9 months ago
Esun Kim	0703276770	[CI] Bazel upgrade (#36104 ) Upgraded Bazel as follows; - Bazel 6.4 to 6.5 - Bazel 7.0 to 7.1 Closes #36104 PiperOrigin-RevId: 616237591	9 months ago
Esun Kim	45aecbe355	[Tool] Added Bazel 7 basic support (#35362 ) - Added Bazel 7 to the support bazel versions. - Changed the default Bazel version to 7. - Fixed Android Binder build issue. Closes #35362 PiperOrigin-RevId: 592946781	12 months ago
Esun Kim	d77e5c0dd3	[Build] Dropped Bazel 5.x and Upgraded Bazel 6.4.0 (#34813 ) - Dropped Bazel 5.x support aligned with [Foundational C++ support policy: Bazel](https://opensource.google/documentation/policies/cplusplus-support). - Upgraded Bazel 6 to 6.4.0 (the latest) - Updated gRPC Bazel documentation to be aligned with the policy above.	1 year ago
Jan Tattermusch	d3548a3941	[bazel] Upgrade bazel repo-wide to 6.3.2 (#34088 ) - Upgrade bazel - Reduce the number of places where bazel version needs to be upgraded in future. - also make sure the list of bazel versions to test by bazelified tests is loaded from supported_versions.txt (it was hardcoded before). - ~~Try upgrading windows RBE build to bazel 6.3.2 as well.~~ The core idea: - the source of truth for supported bazel versions is in `bazel/supported_versions.txt` - the first version listed in `bazel/supported_versions.txt` is considered to be the "primary" bazel version and is going to be used in most places thoroughout the repo. - use templates to include the primary bazel version in testing dockerfiles and in a newly introduced `.bazelversion` files (which gets loaded by our existing `tools/bazel` wrapper). ~~Supersedes https://github.com/grpc/grpc/pull/33880~~	1 year ago
Esun Kim	3bd6c38650	[Infra] Use Bazel 6 and drop Bazel 4 (Part 2) (#32910 ) Oops I missed important changes from https://github.com/grpc/grpc/pull/32712. And it turned out that there are two problems that I couldn't fix at this point. - Windows Bazel RBE Linker Error: This may be caused by how new Bazel 6 invokes build tools chain but it's not clear. I put workaround to use Bazel 5 by using `OVERRIDE_BAZEL_VERSION=5.4.1` - Rule `rules_pods` to fetch CronetFramework from CocoaPod has incompatibility with sort of built-in apple toolchain. (https://github.com/bazel-xcode/PodToBUILD/issues/232): I couldn't find a workaround to fix this so I ended up disabling all tests depending this target.	2 years ago
Esun Kim	6e3dcc0df5	[Infra] Use Bazel 6 and drop Bazel 4 (#32712 ) Let's move on as we'd agreed to drop 4.x	2 years ago
Esun Kim	2915f9fd53	Add Bazel 6 to the list of supported bazel versions (#31940 ) * Bazel 6 * Update doc	2 years ago
Esun Kim	f8de7c8c68	Clean up supported bazel versions (#31067 ) * Bazel versions * Generate docs	2 years ago
Jan Tattermusch	631392f2e7	Upgrade bazel version to bazel 5.3 (repo-wide) (#30844 ) * update bazel to 5.3.0 * regenerate dockerfiles * update bazel distribtest * update docker image templates * regenerate dockerfiles 2 * regenerate bazel_support.md * upgrade rules_apple and apple_support bazel deps * Revert "upgrade rules_apple and apple_support bazel deps" This reverts commit `eb9a0d2155`. * fix objc bazel 5.3 build on kokoro mojave image	2 years ago
Richard Belleville	e79b2a9b32	Add Documentation for Supported Bazel Versions (#29191 ) * Create Bazel support range docs * Review comments * Move supported versions file	3 years ago

11 Commits (1f6978f15581658e8ef6e22d13964b25f05a31bb)