build: updated Docker builds to persist Bazel cache.#2704
Closed
asridharan wants to merge 1 commit intoenvoyproxy:masterfrom
Closed
build: updated Docker builds to persist Bazel cache.#2704asridharan wants to merge 1 commit intoenvoyproxy:masterfrom
asridharan wants to merge 1 commit intoenvoyproxy:masterfrom
Conversation
Using the docker builds is currently painful since the Bazel cache is not persisted. This implies that every build is a clean build and hence the docker build system cannot be used during regular development workflows. In this change have introduced a data-volume to the Docker build system that would persist the Bazel cache across different Docker runs. The name of the data-volumen defaults to `bazel-cache` but can be changed by the developer using the environment variable `ENVOY_DOCKER_BAZEL_CACHE`. Signed-off-by: Avinash Sridharan <avinash.sridharan@gmail.com>
Author
|
closing this PR out for the time being, since didn't realize that we can run the docker build with different users. Currently the solution in this PR is specifically for the |
jpsim
pushed a commit
that referenced
this pull request
Dec 1, 2022
Add unit tests for PlatformBridgeCertValidator Risk Level: Low Testing: Yes :) Docs Changes: N/A Release Notes: N/A Signed-off-by: Ryan Hamilton <rch@google.com> Signed-off-by: JP Simard <jp@jpsim.com>
jpsim
pushed a commit
that referenced
this pull request
Dec 1, 2022
Add unit tests for PlatformBridgeCertValidator Risk Level: Low Testing: Yes :) Docs Changes: N/A Release Notes: N/A Signed-off-by: Ryan Hamilton <rch@google.com> Signed-off-by: JP Simard <jp@jpsim.com>
jpsim
added a commit
that referenced
this pull request
Dec 2, 2022
…/docs/sphinx-5.3.0 * origin/main: (50 commits) ci: Bump mobile build images (#24317) ci: update llvm on bazel CI (#24296) ci: Fix flaky coverage limit (#24320) ci: Fix change detection (part 2) (#24264) Start slow start window on first successful HC, make slow start re-enterable (#23946) contrib-sipproxy: rework sipproxy stats (#24165) build(deps): bump github/codeql-action from 2.1.32 to 2.1.35 (#24292) build(deps): bump node from `c59fb39` to `80844b6` in /examples/ext_authz/auth/http-service (#24274) build(deps): bump actions/upload-artifact from 2 to 3 (#24121) build(deps): bump mysql from `96439dd` to `66efaaa` in /examples/mysql (#24273) build(deps): bump grpcio from 1.50.0 to 1.51.1 in /examples/grpc-bridge/client (#24272) Allow mobile/library/common/jni/ to be built on non-Android platforms. (#24299) generic proxy: added drain support to generic proxy to doing graceful closes on connections when possible (#24220) Reduce Route/VirtualHost memory utilization by avoiding RateLimitPolicy instances when not needed (#24243) Reduce VirtualHost memory utilization by avoiding CatchAllVirtualCluster when not needed (#24182) Fix mobile/tools/check_format.sh to re-apply #2698 (#24300) upstream: don't require `source_address` in `upstream_bind_config` (#24250) Quiche roll 20221201150327 (#24290) Cleanup threading/ownership semantics of PlatformBridgeCertValidator (#2713) Add unit tests of the PlatformBridgeCertValidator (#2704) ... Signed-off-by: JP Simard <jp@jpsim.com>
jpsim
added a commit
that referenced
this pull request
Dec 2, 2022
…/docs/pygments-2.13.0 * origin/main: (25 commits) ci: Bump mobile build images (#24317) ci: update llvm on bazel CI (#24296) ci: Fix flaky coverage limit (#24320) ci: Fix change detection (part 2) (#24264) Start slow start window on first successful HC, make slow start re-enterable (#23946) contrib-sipproxy: rework sipproxy stats (#24165) build(deps): bump github/codeql-action from 2.1.32 to 2.1.35 (#24292) build(deps): bump node from `c59fb39` to `80844b6` in /examples/ext_authz/auth/http-service (#24274) build(deps): bump actions/upload-artifact from 2 to 3 (#24121) build(deps): bump mysql from `96439dd` to `66efaaa` in /examples/mysql (#24273) build(deps): bump grpcio from 1.50.0 to 1.51.1 in /examples/grpc-bridge/client (#24272) Allow mobile/library/common/jni/ to be built on non-Android platforms. (#24299) generic proxy: added drain support to generic proxy to doing graceful closes on connections when possible (#24220) Reduce Route/VirtualHost memory utilization by avoiding RateLimitPolicy instances when not needed (#24243) Reduce VirtualHost memory utilization by avoiding CatchAllVirtualCluster when not needed (#24182) Fix mobile/tools/check_format.sh to re-apply #2698 (#24300) upstream: don't require `source_address` in `upstream_bind_config` (#24250) Quiche roll 20221201150327 (#24290) Cleanup threading/ownership semantics of PlatformBridgeCertValidator (#2713) Add unit tests of the PlatformBridgeCertValidator (#2704) ... Signed-off-by: JP Simard <jp@jpsim.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
build: updated Docker builds to persist Bazel cache.
Description
Using the docker builds is currently painful since the Bazel cache is
not persisted. This implies that every build is a clean build and hence
the docker build system cannot be used during regular development
workflows.
In this change I have introduced a data-volume to the Docker build system
that would persist the Bazel cache across different Docker runs. The
name of the data-volumen defaults to
bazel-cachebut can be changed bythe developer using the environment variable
ENVOY_DOCKER_BAZEL_CACHE.Testing
Ran the docker build
Multiple times to ensure that Bazel cache is persisted across runs which would result in not re-building the entire source from scratch.
Signed-off-by: Avinash Sridharan avinash.sridharan@gmail.com
title: one line description
Description:
Risk Level: Low | Medium | High
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional API Changes:]
[Optional Deprecated:]