CI/CD Integration

CI/CD Integration

Integrate Arxo into your CI/CD pipeline to run Agent Architecture and OpenClaw Architecture analysis, enforce policy gates, and produce JSON or HTML reports.

Guides

Guide	Description
GitHub Actions	Basic setup, caching, reports, and PR comments
GitLab, Jenkins, CircleCI	GitLab CI, Jenkins, and CircleCI examples
Pre-commit Hooks	Run analysis before commits
Docker	Dockerfile and Docker Compose
Configuration & Tips	Config strategies, performance, notifications

Exit codes

Exit Code	Meaning
0	Success — no violations
1	Policy violations detected
2	Configuration error
3	Analysis error
4	Invalid arguments

# Fail on violations
arxo analyze || exit 1

# Fail fast (stop at first violation)
arxo analyze --fail-fast

Best practices

1. Start with loose policies — Tighten gradually.
2. Use a shared config — e.g. .arxo.ci.yaml for consistency.
3. Cache analysis results — Faster CI runs.
4. Generate HTML reports — For visual debugging.
5. Document policies — Why rules exist.

Troubleshooting

• Analysis too slow — Exclude test/build directories in config; cache results; use --path for a smaller subdirectory.
• False positives — Adjust policy thresholds; exclude specific patterns.
• Memory issues — Exclude large dependencies; increase CI machine size.

IDE and MCP

Use the MCP server to run analysis from your IDE or AI assistant. Ask: “Run architecture analysis on this project”. See MCP Workflows and analyze_architecture.

Next steps

• Configuration — Configure policies
• CLI Reference — Command options
• Policy Examples — Real-world policies
• Troubleshooting — Common issues