protobuf

Commit Graph

Author	SHA1	Message	Date
Mike Kruskal	15d2505070	Fix staleness flakes from race condition. If a change is committed while we're regenerating stale files, we should just bail and let the next job handle the refresh. PiperOrigin-RevId: 510453613	2 years ago
Mike Kruskal	d8cd3bd9c9	Tweak GHA names to make failures clearer in dashboard PiperOrigin-RevId: 508944353	2 years ago
Mike Kruskal	364328858e	Tweak GHA names to make failures clearer in dashboard PiperOrigin-RevId: 508944353	2 years ago
Mike Kruskal	8dc14f688c	Migrate daily staleness tests to GHA PiperOrigin-RevId: 507022987	2 years 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	81eebe3fdd	Upgrade upb GHA to large runners PiperOrigin-RevId: 501619842	2 years ago
Mike Kruskal	e3c346fdd8	GitHub Workflows security hardening (#11323 ) Roll forward of #10843 after accidental direct merge Closes #11323 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11323 from mkruskal-google:restore-hardening `ef7c9fd067` PiperOrigin-RevId: 495885677	2 years ago
Protobuf Team Bot	1b64b75716	Clean up a fraction of message.cc to use Emit(). PiperOrigin-RevId: 495646298	2 years ago
Alex	31c3aeeb52	GitHub Workflows security hardening (#10843 ) * build: harden codespell.yml permissions Signed-off-by: Alex <aleksandrosansan@gmail.com> * build: harden generated_cmake.yml permissions Signed-off-by: Alex <aleksandrosansan@gmail.com> * build: harden objc_cocoapods.yml permissions Signed-off-by: Alex <aleksandrosansan@gmail.com> * build: harden php-ext.yml permissions Signed-off-by: Alex <aleksandrosansan@gmail.com> * build: harden update_php_repo.yml permissions Signed-off-by: Alex <aleksandrosansan@gmail.com>	2 years ago
Adam Cozzette	f1998d91a8	Update auto-generation script to handle well-known types I went ahead and deleted the update_file_list.sh script, because (a) there was no good reason for it to be in a separate script and (b) we now need to handle the well-known types in addition to file_lists.cmake. With this change, we just invoke the staleness tests from the main script to update everything. While I was at it I made a couple small fixes: - Don't skip the update step just because the previous commit was by "Protobuf Team Bot". Copybara commits use this name and we still want to do the auto-update step after them. - Include the CL number in the description if the previous commit came from a CL. PiperOrigin-RevId: 487231324	2 years ago
Adam Cozzette	6be96e7a20	Run CMake file auto-generation only on the main protobuf repo (#10611 ) This workflow will otherwise fail on forks, so let's make sure to do it only on the main repo where we need it.	2 years ago
Adam Cozzette	805812ec90	Auto-generate CMake file lists in GitHub action (#10592 ) This GitHub action will run after each pull request merge and will auto-update the file lists in in src/file_lists.cmake. The action will run as our bot account. I realized that if a bug somehow made the file generation non-idempotent, this could trigger an infinite loop of commits, so I put in an extra safeguard against that. If the previous commit was by "Protobuf Team Bot", the GitHub action will revert any local changes to ensure that no new commit will be made.	2 years ago
Mike Kruskal	445a49480c	Adding Github Action to keep CMake generated file lists up to date (#10243 )	2 years ago

3 Commits (78d71cac9f91d80e5f64407d8d9be9586d3e052c)