protobuf

Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/

Mike Kruskal 69c1fa531c Add windows tests for C++ builds (#10364 ) * Adding non-docker builds for protoc in our supported build systems * Tweaking bazel builds * Fixing compatibility with older CMake used by kokoro * Fixing configs to point to proper scripts * Propagate errors up properly * Reinstall Bazel, point NMake to compiler, fix broken static_assert in test * Adding common setup, enabling long paths * Explicitly pick 64-bit compiler * Removing arch from nmake build * Try to upgrade cmake for installation * Enabling 8.3 filename support (https://bazel.build/docs/windows) * Fixing choco calls * Making installation use Release * Switching to batch for common config * Fixing some install test issues unique to Windows * Attempt another way to get shorter Bazel paths * More windows bazel tweaks * Fixing shared library failure from non-exported function used in tests * Use commandline flags instead of bazelrc * Fix line break mismatch * Add .exe extension for test plugin on windows * Add temporary logging * Switch to rootpath over hardcoded system-dependent plugin path * Enabling symlinks/runfiles to fix broken test on windows		2 years ago
..
common	[Kokoro/Bazel] Send Bazel build results to BES. (#10008 )	3 years ago
docs	Update versions for publish python script	2 years ago
linux	Adding shared library build test (#10351 )	2 years ago
macos	Remove distcheck and dist_install Kokoro tests (#10326 )	2 years ago
macos-next	[Kokoro] Add dist check build for linux+cmake (#9939 )	3 years ago
release	Migrating macos php builds from 7.0/7.3 to 7.4/8.0 (#10274 )	2 years ago
windows	Add windows tests for C++ builds (#10364 )	2 years ago
README.md	Enhance explanation in kokoro/README.md. (#8253 )	4 years ago

README.md

Kokoro Infrastructure

The files in this directory serve as plumbing for running Protobuf tests under Kokoro, our internal CI.

We have shared this part of our CI configuration in hopes that it is helpful to contributors who want to better understand the details of our test and release processes. If there are changes, please file an issue; unfortunately, we may not be able to accept PRs (but feel free to send one if it helps to explain the issue).