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

Author	SHA1	Message	Date
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	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
Jan Tattermusch	a526a091ae	[docker images] Consolidate git directory ownership workaround and upgrade ccache (#34035 ) Based on https://github.com/grpc/grpc/pull/34033 Bunch of cleanup and rebuilding many docker images from scratch - consolidate the workaround for "dubious ownership" issue reported by git. Other team members have run into this recently and used similar but not identical workarounds so some cleanup is due. - rebuilding many images increases the chance that we fix the "dubious ownership" git issue early on rather than later on in the one-at-a-time fashion in the future (and the former will prevent many teammembers from wasting time on this weird issue). - Newer version of ccache is needed for some portability tests to be able to benefit from caching (e.g. the GCC 12 portability test to get benefits of local disk caching) - this is a prerequisite for reenabling the bazelified gcc12 portability test. - upgrade node interop images to debian:11 (since debian jessie is long past EOL).	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
Jan Tattermusch	ed39634fe8	Move docker images from dockerhub to artifact registry. (#31591 ) * push_testing_images.sh overhaul * simplify dockerize scripts * update run_in_docker.sh script * add generated .current_version files for docker images * improvements to push_testing_images.sh * add local-only check for push_testing_images.sh to sanity tests * fix sanity check * add expiration for TRANSFER_FROM_DOCKERHUB * add a readme file	2 years ago