Use xargs for publishing nuget packages #134
Open
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.
Currently we use
find
for publishing nuget packages.find
will only exit with a non 0 error code if you fail to traverse a directory.This can lead to a situation whereby the nuget package fails to publish, but we never know about it:
With the addition of the fact that nuget keys expire, we probably need to be notified when nuget publishing fails.
This switches us to use xargs instead