Running in CI / non-interactive environments¶

The exporter automatically detects CI environments and suppresses rich terminal formatting (colors, spinner animations, progress bar redraws) so that log output is clean and readable in CI logs.

Detection is based on two standard environment variables:

Variable	Effect
`CI=true`	Disables ANSI color codes and live terminal output
`NO_COLOR=1`	Same effect (follows the no-color.org convention)

Most CI platforms (GitHub Actions, GitLab CI, CircleCI, Jenkins, etc.) set CI=true automatically.

Missing or invalid credentials¶

In an interactive terminal, missing or rejected credentials open the config menu at the failing instance. In non-interactive runs, cme prints an error to stderr and exits with code 1 instead, so a wrapper or CI job fails fast rather than waiting on a prompt.

A run counts as non-interactive when any of these is true:

CME_NON_INTERACTIVE is set to 1, true or yes
CI is set
stdin is not a terminal

A Confluence-only backup does not need Jira credentials. Disable Jira enrichment so Jira issue links are exported without fetching issue data:

cme config set export.enable_jira_enrichment=false

Controlling log verbosity¶

You can control output verbosity via the CME_EXPORT__LOG_LEVEL env var or the export.log_level config option:

# Enable verbose debug logging for a single run (not persisted):
CME_EXPORT__LOG_LEVEL=DEBUG cme pages <page-url>

# Reduce verbosity permanently:
cme config set export.log_level=WARNING

# Or for the current session only:
CME_EXPORT__LOG_LEVEL=WARNING cme pages <page-url>

This is useful for using different log levels for different environments or for scripting.

Tips for CI pipelines¶

Use a dedicated config file via CME_CONFIG_PATH so CI runs don't share state with developer machines.
Provide credentials via secrets and set them with cme config set at the start of the run, or use ENV var overrides for non-auth options.
Pin the version using the version-specific installer URL; see Installation.