Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: undo some protobuf hacks, put some new ones in. #1299

Closed
wants to merge 1 commit into from

Conversation

htuch
Copy link
Member

@htuch htuch commented Jul 20, 2017

As a bonus, enabled more verbose build of external deps so we don't sit
around for minutes on initial checkout with no activity indicator. This
can be done safely now as everyone should be at Bazel 0.5.2.

* Use protobuf from HEAD to ensure we have the
  protocolbuffers/protobuf#3327 fix for CI and local
  builds. Users can opt to use a specific release tag with the
  ENVOY_PROTOBUF_COMMIT env var.

* Remove the workaround for protocolbuffers/protobuf#3327
  in do_ci.sh.

* Remove the multiple protobuf versions that existed because
  protocolbuffers/protobuf#2508 wasn't merged.

* Add some evil symlink stuff to get @protobuf_bzl inferred from
  wherever WORKSPACE points the envoy_dependencies path at.

As a bonus, enabled more verbose build of external deps so we don't sit
around for minutes on initial checkout with no activity indicator. This
can be done safely now as everyone should be at Bazel 0.5.2.
@htuch
Copy link
Member Author

htuch commented Jul 20, 2017

@mattklein123
Copy link
Member

We probably need to split this into 2 commits?

@htuch
Copy link
Member Author

htuch commented Jul 21, 2017

Yeah, I thought we could try and sneak past that for a few commits, but it's probably best. We actually need 3 commits:

  1. Switch protobuf version, rebuild Docker image.
  2. Update build system etc.
  3. Remove dual build of thirdparty in Docker image.

@htuch
Copy link
Member Author

htuch commented Jul 21, 2017

Closing out to split the commits.

@htuch htuch closed this Jul 21, 2017
jpsim pushed a commit that referenced this pull request Nov 28, 2022
Description: On bazel 3.7.2 we no longer can see Java error output in builds. Downgrading for now, since this significantly impedes development and debugging.
Risk Level: Low
Testing: Local & CI

Signed-off-by: Mike Schore <mike.schore@gmail.com>
Signed-off-by: JP Simard <jp@jpsim.com>
jpsim pushed a commit that referenced this pull request Nov 29, 2022
Description: On bazel 3.7.2 we no longer can see Java error output in builds. Downgrading for now, since this significantly impedes development and debugging.
Risk Level: Low
Testing: Local & CI

Signed-off-by: Mike Schore <mike.schore@gmail.com>
Signed-off-by: JP Simard <jp@jpsim.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants