JENKINS-22450 - Make trx and coverage files paths available to further build steps in VSTestRunner plugin #2
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
|
plugins » vstestrunner-plugin #6 SUCCESS |
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
yasu-s
added a commit
that referenced
this pull request
Aug 31, 2014
JENKINS-22450 - Make trx and coverage files paths available to further build steps in VSTestRunner plugin
egoughnour
added a commit
that referenced
this pull request
Apr 2, 2018
update from jenkinsci/master
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.
Proposed change pumps console output and catches trx and coverage files and then publishes them to next build steps via VSTEST_RESULT_TRX and VSTEST_RESULT_COVERAGE environment variables.