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

Step 1, build 3.7.2 bazel toolchains #114

Merged
merged 6 commits into from
Dec 17, 2020

Conversation

wrowe
Copy link
Contributor

@wrowe wrowe commented Nov 21, 2020

Build with envoy toolchain for bazel 3.7.2.

  • Follow this to adopt bazel 3.7.2 for envoy upon its release
  • then we will bump /bazelbuild/envoy/WORKSPACE to pick up bazel 3.7.2 and validate
  • then we wait hours for all builds in flight before proceeding to add llvm 11.0.0 in Windows to a rebuild of the 3.7.2 envoy build tools alone

Co-authored-by: Sunjay Bhatia sunjayb@vmware.com

Follow this with adopting bazel 3.7.1 for envoy, wait hours for all builds in flight

Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Co-authored-by: Sunjay Bhatia <sunjayb@vmware.com>
Co-authored-by: William A Rowe Jr <wrowe@vmware.com>
@wrowe wrowe requested a review from a team as a code owner November 21, 2020 01:35
@wrowe wrowe marked this pull request as draft November 21, 2020 01:36
@wrowe
Copy link
Contributor Author

wrowe commented Nov 21, 2020

This PR is staged as a draft, awaiting the announcement of bazel 3.7.1 perhaps Tuesday.

toolchains/regenerate.sh Outdated Show resolved Hide resolved
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
…lvm11

Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
@sunjayBhatia
Copy link
Member

/retest

@sunjayBhatia
Copy link
Member

Blocked on bazelbuild/bazel#12545 as well

@wrowe wrowe changed the title Step 1, build 3.7.1 bazel toolchain Step 1, build 3.7.2 bazel toolchains Dec 14, 2020
@wrowe
Copy link
Contributor Author

wrowe commented Dec 14, 2020

Blocked on bazelbuild/bazel#12545 as well

This fix is picked up in Bazel 3.7.2rc1 which we expect be released, this week. Updating migration patches now for this switch, and testing locally against 3.7.2 candidate.

@wrowe
Copy link
Contributor Author

wrowe commented Dec 17, 2020

/retest

@sunjayBhatia
Copy link
Member

@wrowe I don't think the /retest command and repokitteh are set up for this repo, probably have to just push an empty commit

Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
@sunjayBhatia sunjayBhatia marked this pull request as ready for review December 17, 2020 19:38
@sunjayBhatia sunjayBhatia requested a review from lizan December 17, 2020 19:38
@wrowe wrowe mentioned this pull request Dec 17, 2020
@lizan lizan merged commit 16d0083 into envoyproxy:master Dec 17, 2020
htuch pushed a commit that referenced this pull request Dec 17, 2020
  [skip ci]
  build 3.7.2 bazel toolchains (#114)

Build with envoy toolchain for bazel 3.7.2.

Follow this to adopt bazel 3.7.2 for envoy upon its release
then we will bump /bazelbuild/envoy/WORKSPACE to pick up bazel 3.7.2 and validate
then we wait hours for all builds in flight before proceeding to add llvm 11.0.0 in Windows to a rebuild of the 3.7.2 envoy build tools alone

Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
Co-authored-by: Sunjay Bhatia <sunjayb@vmware.com>
htuch pushed a commit that referenced this pull request Dec 17, 2020
  [skip ci]
  Regenerate linux toolchains from 16d0083

  [skip ci]
  build 3.7.2 bazel toolchains (#114)

Build with envoy toolchain for bazel 3.7.2.

Follow this to adopt bazel 3.7.2 for envoy upon its release
then we will bump /bazelbuild/envoy/WORKSPACE to pick up bazel 3.7.2 and validate
then we wait hours for all builds in flight before proceeding to add llvm 11.0.0 in Windows to a rebuild of the 3.7.2 envoy build tools alone

Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
Co-authored-by: Sunjay Bhatia <sunjayb@vmware.com>
@wrowe wrowe deleted the bump-bazel-before-llvm11 branch December 17, 2020 22:19
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.

3 participants