User/regisb/fix mux release pipeline fragility5#4530
Merged
Conversation
RBrid
added
the
area-DevInternal
ghost
added
the
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ranjeshj
added
team-Controls
ranjeshj
approved these changes
Mar 15, 2021
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
2 participants
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.
The MUX-Release pipeline recently failed because of a robocopy fragility. Sometimes its process exit code isn't 0 even though it apparently succeeded. We already had a workaround in place for code 1 and 3 but not code 2.
In this case error code 2 was returned: [error]Process completed with exit code 2.
So I am adding the same workaround.
The MergeNupkgParts.cmd script actually had succeeded earlier in the same pipeline, so it really is a fragility issue.