monitor-ci

Automated CI monitoring tracks your Nx Cloud pipeline executions and applies self-healing fixes for common failures. It manages status checks, generates fixes, verifies them locally, and applies them via MCP to reduce manual intervention.

Automated self-healing targets common CI failures like environment issues and outdated lockfiles. When a pull request fails, it detects the error, attempts dependency updates, and re-runs the CI to confirm the fix without developer intervention.

CI pipeline monitoring supports configurable timeouts and verbosity levels. You can adjust these settings to control how long the monitoring runs and how detailed the status check logs are during the self-healing process.

Throttled self-healing limits the frequency of automated fix attempts for CI failures. This prevents excessive fix generation and local verification loops when environment issues or pre-CI-attempt failures persist continuously.

Yes, this CI monitoring requires Nx Cloud to function, as it continuously tracks the status of Nx Cloud CI pipeline executions to detect failures and trigger the automated self-healing workflow.

Automated self-healing is limited to common CI failures like environment issues and lockfile updates, and it applies throttled self-healing to prevent excessive retries. Complex logic errors or custom infrastructure failures require manual developer intervention.