Fix Publisher JUnit output to Slave workspace#150
Merged
undera merged 1 commit intojenkinsci:masterfrom Dec 12, 2017
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #150 +/- ##
==========================================
+ Coverage 68.3% 68.33% +0.03%
==========================================
Files 44 44
Lines 3896 3894 -2
Branches 678 677 -1
==========================================
Hits 2661 2661
+ Misses 989 987 -2
Partials 246 246
Continue to review full report at Codecov.
|
Contributor
Author
|
@undera Can you guys please merge this fix before the 3.4 release? Thanks |
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
3 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.
Fix:
When running on a Slave node, the Performance Publisher's JUnit output file would not be written to the (remote) workspace correctly.