commit | 0731090067d68e9892488884fbee00cbd19f131a | [log] [tgz] |
---|---|---|
author | Dmitry Ivankov <dmitry.ivankov@cognite.com> | Tue Oct 06 14:44:25 2020 +0200 |
committer | Yun Peng <pcloudy@google.com> | Fri Oct 09 10:21:50 2020 +0200 |
tree | 36014a8f6432d87c8a10b216589eef08d6b34012 | |
parent | 199e70c11716cccf098f06b50c98d4f44df08b53 [diff] |
[1/3] Bump grpc from 1.26.0 to 1.31.1 PART 1: prepare third_party/grpc files for new version Composed PR: https://github.com/bazelbuild/bazel/pull/12226 Note: generate_cc.bzl and protobuf.bzl are modified in place and already affect the build. But the change seems to be harmless (adding explicit ProtoInfo load from @rules_proto). Fixes having external dependencies without checksum - boringssl (each download was timestamped, but otherwise stable) - bazel_skylark was overriden to be master (sic!) There doesn't seem to be many breaking/big changes up to grpc 1.31.1 - removal of xds-experimental URI scheme - removal of MAX_EPOLL_EVENTS_HANDLED_EACH_POLL_CALL - enable TLS 1.3 in the C-core and all wrapped languages - some of bazel-related patches got merged in https://github.com/grpc/grpc/releases How to check whether certain dependency has a checksum bazel query //external:bazel_skylib --output build bazel query //external:boringssl --output build How to find (almost?) all problematic dependencies compare output of bazel query 'kind(http_archive, //external:all) + kind(http_file, //external:all) + kind(distdir_tar, //external:all)' --output xml | xq '.query.rule[] | ."@name"' vs bazel query 'kind(http_archive, //external:all) + kind(http_file, //external:all) + kind(distdir_tar, //external:all)' --output xml | xq '.query.rule[] | select (.string[]."@name" | contains("sha256")) | ."@name"' Note that it looks for string sha256 and misses dict sha256 for distdir_tar rules - those are false positive currently. Closes https://github.com/bazelbuild/bazel/pull/12235
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md