-
Notifications
You must be signed in to change notification settings - Fork 101
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
this reverts previous breakage of coverage functionality. coverage functionality is now turned off for all circleci jobs
- Loading branch information
Showing
3 changed files
with
4 additions
and
9 deletions.
There are no files selected for viewing
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
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
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
dfe88b8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@leej3
Why does this need to be turned on? We (including @afni-rickr ) were alerted about severe codecov security issues, and we turned it off because of that. Isn't codecov separate from CircleCI, and so can't we leave it off for testing for now? If not, why not? (And if not, can we change things so it can be?)
dfe88b8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or am I misreading what this commit does? The commit string is "turn off codecov..." but this commit uncomments a commenting out that we had made to definitely turn it off. Sorry if I am misinterpreting, but due to the security risks of CodeCov, we have to be careful.
dfe88b8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it turns off the code coverage testing but the functionality is left intact so that tests of that functionality do not fail. It also means that people can still run coverage testing locally if they wish.