R CMD INSTALL and install.packages() structured logging for CI/CD failure classification

There is no documented configuration option or environment variable that enables R CMD INSTALL or install.packages() to emit machine-readable output (such as JSON). These tools are designed for human-readable stdout/stderr, and there is no stable, version-agnostic mapping of exit codes to specific failure classes.

Analysis of Base Installation Behavior

The base installation pathway in R lacks a structured diagnostic API. The following constraints apply to CI/CD classification efforts:

• Binary Exit Codes: R generally returns a binary status (0 for success, non-zero for failure). It does not provide granular exit codes to distinguish between a network timeout, a missing libc dependency, or a C++ compiler mismatch.
• Fragile Log Patterns: Error messages are generated by a mix of R internals and external system tools (make, gcc, clang). Because these messages vary by OS, R version, and system locale, regex-based classification is inherently brittle.
• Lack of Native Artifacts: Neither the R binary nor the internal installation functions produce structured metadata files (like build.json) by default.

Implementation Path for CI/CD Classification

Since structured output cannot be enabled via configuration, you must wrap the installation process to synthesize the required metadata. To avoid replacing the base pathway, use a wrapper script that captures the output and maps it to failure classes.

Recommended Wrapper Strategy

1. Capture Output: Redirect stdout and stderr to a temporary log file.
2. Execute Installation: Run the standard R CMD INSTALL or install.packages() command.
3. Post-Process for Heuristics: Use a script to scan the log for high-confidence markers. While fragile, these are the only available signals:
   • Network: Search for cannot open URL or timeout.
   • System Dependencies: Search for configuration failed for package or fatal error: [header].h: No such file or directory.
   • Compiler/Version: Search for std:: errors or version mismatch.
4. Emit JSON: The wrapper script should output a JSON object containing the exit code, the detected class, and the raw log snippet.

Verification Command

To confirm the absence of structured flags in your specific environment, run:

R CMD INSTALL --help | grep -Ei "json|structured|machine"

Uncertainties and Assumptions

This assessment assumes the use of standard CRAN/Bioconductor installation pathways. If your pipeline uses custom configure scripts within packages, those scripts may provide their own logging, but they do not integrate into a global R structured logging framework.

Missing Diagnostic Detail: Are you using a specific containerized environment (e.g., Rocker) or a managed R environment? Some environment-specific build tools provide their own wrapper logs that might offer more context than the base R output.