Add ability to change the output path from /rcov#9
Open
TALlama wants to merge 1 commit intofguillen:masterfrom
Open
Add ability to change the output path from /rcov#9TALlama wants to merge 1 commit intofguillen:masterfrom
/rcov#9TALlama wants to merge 1 commit intofguillen:masterfrom
Conversation
|
I ran into this when using simplecov-rcov on Gitorious as well. Here's what we ended up doing: https://gitorious.org/capillary/capillary_rb/merge_requests/7 This functionality would be quite nice to have in simplecov-rcov. It would be even cooler if simplecov-rcov provided an equivalent "rcov" task to rake that did this. |
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 default remains unchanged, but the path can now be changed by setting the
SIMPLECOV_RCOV_RESULTS_PATHenvironment variable.In my case, I want to set it to an empty string so that the coverage report will show up in the same place in a SimpleCov-using 1.9 branch as it does in my Rcov-using 1.8 branch as we do the transition. This is important because Jenkins looks in one place of the coverage file, and the same job is processing both branches.