Integrations

Architecture feedback where engineering already happens.

ArchUnit libraries work as code and tests. That keeps adoption close to source control, project configuration, familiar runners, and the continuous integration path.

Test frameworks

Keep architecture feedback in the runner developers already understand.

  • Jest
  • Vitest
  • Jasmine
  • pytest
  • .NET test
  • RSpec
  • Cargo test

Continuous integration

Run architecture rules with the same commands used on a workstation.

  • GitHub Actions
  • GitLab CI/CD
  • Jenkins
  • Azure Pipelines
  • CircleCI

Project systems

Resolve the configuration and module model that governs the real codebase.

  • tsconfig
  • Python packages
  • MSBuild
  • Bundler
  • Cargo
  • Go modules

Delivery workflows

Connect a failed rule to the review and ownership process around it.

  • Pull requests
  • Merge requests
  • Quality gates
  • Monorepos
  • Release pipelines

Fit, then scale

Keep the first integration boring.

Use the test runner and CI path you already trust. Add richer reporting and shared policy after the core feedback loop works.