You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running continuous integration builds on a Jenkins server and need the R CMD check output to remain in the project working directory. Otherwise, I can't diagnose the issues on build failures.
I've tried a couple of approaches, including passing check(..., args=c('--output', 'my_check_dir')). The problem is, I'm pretty sure devtools overrides the path separately, resulting in a conflict.
The text was updated successfully, but these errors were encountered:
It doesn't look like it. What about patching check() to return r_cmd_check_path in the case of failure, and then you could add custom handling? Alternatively, we could add the check_dir param to check() and pass that on down to check_r_cmd()
I'm running continuous integration builds on a Jenkins server and need the
R CMD check
output to remain in the project working directory. Otherwise, I can't diagnose the issues on build failures.I've tried a couple of approaches, including passing
check(..., args=c('--output', 'my_check_dir'))
. The problem is, I'm pretty suredevtools
overrides the path separately, resulting in a conflict.The text was updated successfully, but these errors were encountered: