[ci] Ensure logs and artifacts get published on failed builds. #876
Conversation
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
moljac
approved these changes
Apr 19, 2024
Contributor
moljac
left a comment
moljac
left a comment
There was a problem hiding this comment.
I'll have to trust you on this one.
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.
After migrating to the 1ES template, when our build fails, no logs or artifacts are retained, making it very hard to diagnose the issue. Add an
alwayscondition to the output upload so these will get saved.Example build demonstrating artifacts are uploaded on failure:
https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=9440304&view=results