protobuf

Commit Graph

Author	SHA1	Message	Date
Joshua Haberman	5cfc9e775d	Breaking Change: Dropped support for Ruby DSL, [as previously announced](https://engdoc.corp.google.com/eng/doc/devguide/proto/news/2023-12-27.md#ruby-breaking-changes ). The generated code has not used the DSL since 23.0 (released May 8, 2023). PiperOrigin-RevId: 595481605	11 months ago
Mike Kruskal	571b727cb6	Make rules_ruby a dev-only dependency. There is no canonical rules_ruby repo today, and we don't want our fork to become one. In order to unblock inclusion of Protobuf in the bzlmod registry, we're making this a dev dependency and dropping support for Bazel/Ruby. Fixes #14569 PiperOrigin-RevId: 584393841	1 year ago
Adam Cozzette	5ca84008fc	Move utf8_range into the protobuf repo This makes third_party/utf8_range no longer a Git subtree, but instead the permanent location and source of truth for utf8_range. It is also now incorporated into the @com_google_protobuf Bazel repo. Utf8_range still has its own separate CMake build for now, though. PiperOrigin-RevId: 580682733	1 year ago
Jason Lunn	c52d80cf04	Ruby FFI implementation (#13343 ) Supersedes #11483. Closes #13343 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/13343 from protocolbuffers:simultaneous_ffi `bcb4bb7842` PiperOrigin-RevId: 550782245	1 year ago
Mike Kruskal	de903d41fc	Migrate Bazel C++ Linux tests to Github Actions (#11702 ) This is a proof of concept that we can experiment with before migrating all of our Kokoro tests to GHA. In addition to the migration, this builds out infrastructure for safe handling of both external and internal contributions. Two of the existing GHA workflows have also been migrated to this system to unify how we handle testing. To test the new workflow introduced here, you can open PRs to the `gha` branch. This feature branch acts as a staging area for GHA. PRs opened up from this repo will automatically have all tests run on each commit. We will also run them all as post-submits, and continuously on a daily schedule. PRs opened from forked repos will need per-commit approval for each test run, which can be given by adding the `safe for tests` label. Examples (failures are intentional to show that the PR code is being tested): - Internal PR: https://github.com/protocolbuffers/protobuf/pull/11679 - Fork PR (approved): https://github.com/protocolbuffers/protobuf/pull/11685 - Fork PR (rejected): https://github.com/protocolbuffers/protobuf/pull/11683 - External PR: https://github.com/protocolbuffers/protobuf/pull/11695 Closes #11702 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11702 from protocolbuffers:gha `f3a2663896` PiperOrigin-RevId: 506169444	2 years ago
Mike Kruskal	e207bcd940	Migrate ruby release targets to genrule to work around Bazel 5 bug (#11619 ) sh_binary doesn't treat its data dependencies correctly prior to Bazel 6 (see https://github.com/mkruskal-google/protobuf/pull/new/ruby_release) Closes #11619 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11619 from mkruskal-google:ruby_release `f91352a479` PiperOrigin-RevId: 503564788	2 years ago
deannagarcia	5b27b4f300	Add ruby release targets (#11468 ) Add bazel targets to create ruby release artifacts. Should be run with: ``` bazel run ruby:release bazel run ruby:jruby_release ``` Closes #11468 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11468 from deannagarcia:rubyTargets `b7b7eb6865` PiperOrigin-RevId: 503277136	2 years ago
Mike Kruskal	633e8f75d0	Bazelify ruby runtime (#10525 ) This uses https://github.com/protocolbuffers/rules_ruby to fully Bazelify our ruby runtime code. The Rakefile is left in place for now and is still used by our aarch64 tests. With the current implementation ruby behaves similarly to our python wrapper, which selects whatever version is installed in the system. Future enhancements will allow for more hermetic builds via Bazel flags to pin a specific version Closes #10525 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/10525 from mkruskal-google:rules_ruby `97fa1f70ab` PiperOrigin-RevId: 499283908	2 years ago
Mike Kruskal	b81def1cbd	Migrate ruby and php to the new utf8_range repo	2 years ago
Joshua Haberman	d3995ec400	Added staleness test to keep ruby-upb.{c,h} amalgamation files in sync with upb repo (#10496 ) * Added staleness test for ruby-upb.{c,h} and updated. * Removed file comment markers, too much trouble for too little benefit. * Ran clang-format. * Updated ruby-upb.{c,h}. * Added missing table code to amalgamation. * Updated to latest upb, patch no longer needed. * Reverted changes to third_party sub-modules. * Added missing unicode file. * Removed conformance failures for Ruby.	2 years ago
Mike Kruskal	ed5c57a574	Remove all autotools usage (#10132 ) * Bazelfying conformance tests Adding infrastructure to "Bazelify" languages other than Java and C++ * Delete benchmarks for languages supported by other repositories * Bazelfying benchmark tests * Bazelfying python Use upb's system python rule instead of branching tensorflow * Bazelfying Ruby * Bazelfying C# * Bazelfying Objective-c * Bazelfying Kokoro mac builds * Bazelfying Kokoro linux builds * Deleting all deprecated files from autotools cleanup This boils down to Makefile.am and tests.sh and all of their remaining references * Cleanup after PR reorganizing - Enable 32 bit tests - Move conformance tests back - Use select statements to select alternate runtimes - Add internal prefixes to proto library macros * Updating READMEs to use bazel instead of autotools. * Bazelfying Kokoro release builds * First round of review fixes * Second round of review fixes * Third round of review fixes * Filtering out conformance tests from Bazel on Windows (b/241484899) * Add version metadata that was previously scraped from configure.ac * fixing typo from previous fix * Adding ruby version tests * Bumping pinned upb version, and adding tests to python CI	2 years ago
David L. Jones	95da0ba5b4	Rename all BUILD files to BUILD.bazel (#9892 ) This avoids conflicting names in a couple of cases. 1. Within google, we want to sync files but not name them BUILD (since the structure doesn't match). 2. On case-insensitive filesystems, `build` may be used for a build directory. Naming `BUILD.bazel` avoids potentioal conflicts.	3 years ago
Joshua Haberman	dc4aad931e	Sync from Piper @444600173 PROTOBUF_SYNC_PIPER	3 years ago
David L. Jones	d76f8c868c	Add source distribution packaging rules (#9835 ) This change adds `rules_pkg`-based targets that will produce source distribution archives, similar to `make dist`. These rules produce nearly the same outputs as `make dist`. However, there are some differences and caveats: 1. The outputs do not contain vendored googletest sources. 2. You have to run `autogen.sh` before `blaze build pkg:all`. This produces several autotools-related files directly into the source tree. 3. The output .zip files do not have a directory prefix like `protobuf-3.20.1-rc-1` (this will be addressed after [Substitute package variables in `pkg_zip#package_dir`. bazelbuild/rules_pkg#577](https://github.com/bazelbuild/rules_pkg/pull/577); the tar files do have this prefix, though.) 4. One file is missing from the archives, which is produced during the `make` build: benchmarks/gogo/cpp_no_group/cpp_benchmark.cc 5. In several places, I have explicitly excluded some files that are not in the autotools distribution outputs. I think most of those files should probably be included, but for now, I'm aiming for parity with `make dist`. These are marked with comments, so it should be easy to clean them up later.	3 years ago

12 Commits (1d143b5d7ed9e60e6118df38e10e7388735c6d43)