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

Author	SHA1	Message	Date
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	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
Jan Tattermusch	6d3c45ff7b	Add dockerized ARM64 tests (bazel C/C++, C#, PHP, ruby, python) (#28966 ) * C# arm64 docker image * add ruby arm64 docker image * add bazel_arm64 docker image * add python arm64 image * add php arm64 docker image * regenerate * add support for running arm64 tests with run_tests.py * restrict arm64 testing to python3.9 * first version of bazel arm64 C++ tests * add arm64 job configs * add initial checks to push_testing_images.sh	3 years ago