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

Author	SHA1	Message	Date
Mike Kruskal	0ed65fd08f	Enable github caching of Bazel's repository cache. This should substantially reduce network flakes, since most builds will no longer need to download external dependencies. Because these caches actually get pretty expensive (~300 MB just from 1 openjdk dependency), we've taken some precautions: 1) The caches only get updated on push events (i.e. post-submit jobs) 2) Only a single job will push a new cache for any os/branch/commit combination. This will be whichever job finishes its bazel run first, and also has updates for the cache. Over time, the cache should expand to the full set of transitive dependencies as the quicker jobs stop pushing updates. 3) A clear_caches workflow has been introduced to reset the caches in case they grow too large. This will run monthly for now, but can also be run manually. PiperOrigin-RevId: 508133044	2 years ago
Mike Kruskal	c399aeccc4	Enable ccache for CMake builds. This uses ccache + github caching to substantially decrease the time it takes to run CMake builds. Due to Bazel caching, these are some of our slowest tests, causing one of the biggest presubmit bottlenecks PiperOrigin-RevId: 507667813	2 years ago
Mike Kruskal	ae4c4ea6d4	Pin X-code version on mac/bazel tests to prevent flakiness. See https://github.com/bazelbuild/rules_swift/issues/950 and https://www.smileykeith.com/2021/03/08/locking-xcode-in-bazel/ for more details. PiperOrigin-RevId: 507609630	2 years ago
Mike Kruskal	f1e746c491	Migrate remaining Windows tests to GHA PiperOrigin-RevId: 506766851	2 years ago
Mike Kruskal	f0ef44d1e1	Migrate remaining macOS tests to GHA actions PiperOrigin-RevId: 506744609	2 years ago
Mike Kruskal	6816da50cf	Migrate non-Linux C++ tests to GHA actions PiperOrigin-RevId: 506683178	2 years ago
Mike Kruskal	2b4e4260f0	Migrate to composite GHA actions (#11718 ) This migrates from reusable workflows to composite GHA actions. This has the following advantages: 1) We can split them into smaller, easier to reason about chunks 2) We can reuse them more freely between each other and workflows 3) They don't complicate the job names 4) In theory they'll be easier to test in isolation. While composite actions can't be unit-tested, we can easily break them up into nodejs or docker actions that can be. As a proof of concept, some of our non-Bazel tests are migrated to GHA as well (CMake + Composer) Closes #11718 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11718 from protocolbuffers:gha-actions 5403307bc00616e94816aa460813939d8f37a1bd PiperOrigin-RevId: 506375417	2 years ago