Windows CI: Upload test results to AZP #14083
Merged
Conversation
This file contains 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
sunjayBhatia
changed the title
|
@envoyproxy/windows-dev |
|
See https://dev.azure.com/cncf/envoy/_build/results?buildId=57958&view=ms.vss-test-web.build-test-results-tab should be able to filter now for windows test results |
- Requires removing --output_base flag to Bazel startup options - The TEST_TMPDIR and BUILD_DIR bind mounts from the host are where Bazel will place build output etc. - Allowing Bazel to place build and test output there will give the host access to the data to upload Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
CI no longer will use C:/_eb as an output base Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
|
/wait trying to minimize path length increases |
Ensure local builds still work out of the box Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com> Co-authored-by: William A Rowe Jr <wrowe@vmware.com>
|
/retest |
|
Retrying Azure Pipelines: |
…-results Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
|
merged master to get coverage to hopefully pass, shouldnt be affected by this change |
lizan
approved these changes
Nov 20, 2020
andreyprezotto
pushed a commit
to andreyprezotto/envoy
that referenced
this pull request
Nov 24, 2020
- Requires removing --output_base flag to Bazel startup options - The TEST_TMPDIR and BUILD_DIR bind mounts from the host are where Bazel will place build output etc. - Allowing Bazel to place build and test output there will give the host access to the data to upload Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com> Co-authored-by: William A Rowe Jr <wrowe@vmware.com>
qqustc
pushed a commit
to qqustc/envoy
that referenced
this pull request
Nov 24, 2020
- Requires removing --output_base flag to Bazel startup options - The TEST_TMPDIR and BUILD_DIR bind mounts from the host are where Bazel will place build output etc. - Allowing Bazel to place build and test output there will give the host access to the data to upload Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com> Co-authored-by: William A Rowe Jr <wrowe@vmware.com> Signed-off-by: Qin Qin <qqin@google.com>
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: Upload test results to AZP
Bazel will place build output etc.
access to the data to upload
to the exec root/output base Bazel uses
uploaded to AZP so we can track failures over time
Additional Description: N/A
Risk Level: Low
Testing: N/A, CI change
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A