Merged
Conversation
- Watch for //source/exe:envoy-static or empty args to trigger the build
- Treat arbitrary args as bazel test directives
This allows forms such as;
ci/windows_ci_steps.sh //source/exe:envoy-static - build the binary, nothing else
ci/windows_ci_steps.sh //test/... - test everything with exceptions and flake processing
The default (no args) does both of the above, and checks unused deps under bazel/... that are not skip_on_windows
ci/windows_ci_steps.sh //test/common/... - test everything with no exceptions below common
ci/windows_ci_steps.sh //test/common/... --test_tag_filters=-skip_on_windows
- same as above, avoiding broken components under common
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
2bd88bb to
b0aa7b2
Compare
Contributor
Author
|
Note, that this commit moves //bazel/... to the end of the build. Yes, we want to ensure we catch anything dropped in on bazel/foreign_cc or bazel/external, but we don't have to delay 98% of all PR's to look at this upfront. Fail faster in the general case. |
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
davinci26
suggested changes
May 24, 2021
Member
davinci26
left a comment
There was a problem hiding this comment.
LGTM, thanks!
Do you mind also updating the docs at bazel\Readme.md and ci\Readme.md
…args Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
- If building an 18 month old envoy, an 18 month old copy of this document is present in that source tarball - Offer a more recognizable symlink/path advisory based on current Python release Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
…args Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
- Bazel before 5.0.0 fails to shorten executable path names of a specific length. - SymInitialize() fails to load the executable paths of a specific length - abesil tries to prepare for crash analysis and silently continue on failure - grps tries and abruptly aborts the program if symbols cannot be loaded Fix is in for the next bazel rolling release of the 5.0.0 series Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
…args Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Contributor
Author
|
@mattklein123 this is ready with the fix to the three too-long-named borken //test/... entities, let's see if CI passes and merge if so. Will come back after bazel 5.0.0 is in our rbe to re-enable these. |
davinci26
approved these changes
Jun 4, 2021
Member
davinci26
left a comment
There was a problem hiding this comment.
LGTM, can you open an issue so we remember to turn these tests back on
mattklein123
approved these changes
Jun 4, 2021
This was referenced Jun 4, 2021
lizan
pushed a commit
that referenced
this pull request
Jun 25, 2021
* Windows: Expand functionality of ci/windows_ci_steps.sh - Watch for //source/exe:envoy-static or empty args to trigger the build - Treat arbitrary args as bazel test directives This allows forms such as; ci/windows_ci_steps.sh //source/exe:envoy-static - build the binary, nothing else ci/windows_ci_steps.sh //test/... - test everything with exceptions and flake processing The default (no args) does both of the above, and checks unused deps under bazel/... that are not skip_on_windows ci/windows_ci_steps.sh //test/common/... - test everything with no exceptions below common ci/windows_ci_steps.sh //test/common/... --test_tag_filters=-skip_on_windows - same as above, avoiding broken components under common * Update bazel/README.md - If building an 18 month old envoy, an 18 month old copy of this document is present in that source tarball - Offer a more recognizable symlink/path advisory based on current Python release * Clarify windows_build_steps.sh and windows docker invocation * Skip three longest windows test names for the month - Bazel before 5.0.0 fails to shorten executable path names of a specific length. - SymInitialize() fails to load the executable paths of a specific length - abesil tries to prepare for crash analysis and silently continue on failure - grps tries and abruptly aborts the program if symbols cannot be loaded Fix is in for the next bazel rolling release of the 5.0.0 series Signed-off-by: Dmitri Dolguikh <ddolguik@redhat.com> Co-authored-by: William A Rowe Jr <wrowe@vmware.com>
leyao-daily
pushed a commit
to leyao-daily/envoy
that referenced
this pull request
Sep 30, 2021
* Windows: Expand functionality of ci/windows_ci_steps.sh - Watch for //source/exe:envoy-static or empty args to trigger the build - Treat arbitrary args as bazel test directives This allows forms such as; ci/windows_ci_steps.sh //source/exe:envoy-static - build the binary, nothing else ci/windows_ci_steps.sh //test/... - test everything with exceptions and flake processing The default (no args) does both of the above, and checks unused deps under bazel/... that are not skip_on_windows ci/windows_ci_steps.sh //test/common/... - test everything with no exceptions below common ci/windows_ci_steps.sh //test/common/... --test_tag_filters=-skip_on_windows - same as above, avoiding broken components under common * Update bazel/README.md - If building an 18 month old envoy, an 18 month old copy of this document is present in that source tarball - Offer a more recognizable symlink/path advisory based on current Python release * Clarify windows_build_steps.sh and windows docker invocation * Skip three longest windows test names for the month - Bazel before 5.0.0 fails to shorten executable path names of a specific length. - SymInitialize() fails to load the executable paths of a specific length - abesil tries to prepare for crash analysis and silently continue on failure - grps tries and abruptly aborts the program if symbols cannot be loaded Fix is in for the next bazel rolling release of the 5.0.0 series Signed-off-by: William A Rowe Jr <wrowe@vmware.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.
Commit Message: Windows ci add bazel args
Additional Description:
The linux do_ci.sh script has it's own unique syntax, earlier represented in windows_ci_steps.ps1.
It turns out this isn't the most obvious syntax, but bazel instead, as the macos_ci_steps.sh script
uses.
Enhance windows_ci_steps.sh to default to //source/exe:envoy-static + //test/... as was the current
default behavior, but recognize either of these independently, or allow pretty much any bazel
target to be named on the command line for development and diagnostics.
Risk Level: low
Testing: local msvc
Docs Changes: TBD
Release Notes: TBD
Platform Specific Features: Windows build only