CloudBuild non ephemeral worker for Bazel

[yerinu2019]

As a monorepo size using Bazel becomes bigger, Cloud Build non ephemeral worker becomes slower to download and initialize Bazel toolchains and third party Bazel rules. Bazel remote cache and execution do not help to reduce this time and cost. It takes Bazel build and test 10 times longer than local Bazel Build.in CloudBuild.

Is there any way to use non ephemeral worker machine pool for Bazel build?

Thanks.

[Marramirez]

Hello @yerinu2019!

Welcome to the Google Cloud Community!

You can check out the best practices for speeding up builds. It shows how you can speed up your build process, you can test the following practices:

• Building leaner containers
• Using Kaniko Cache
• Using a cached Docker image
• Caching directories with Google Cloud Storage
• Avoiding the upload of unnecessary files

Also, look into this Stack Overflow post about how to speed up bazel builds in Google Cloud Platform. If the above options don't work, you can contact Google Cloud Support to further look into your case. Let me know if it helped, thanks!