Integrations & Automation

Wire Chainsaw into your pipelines and manage it as code — CI/CD enforcement, YAML config-as-code, and custom hook scripts.

Chainsaw is most effective when it is part of your automation, not a console someone visits. This section covers gating CI/CD on the proxy, version-controlling your configuration as YAML, and extending the proxy pipeline with custom validation hooks.

Config-as-code first. Managing repositories, policies, and exceptions as version-controlled YAML makes every change reviewable and reproducible — and lets you promote config between environments like any other code.

CI/CD

Integrate Chainsaw with CI/CD pipelines — the combined reference for GitHub Actions, GitLab CI, and Jenkins.

Per-CI guides

Route GitHub Actions builds through Chainsaw — repository secrets + a PR-gating example.
Route GitLab CI builds through Chainsaw — masked CI/CD variables + a merge-request gating example.
Route Jenkins builds through Chainsaw — withCredentials declarative pipeline.
Route CircleCI builds through Chainsaw — pattern guidance (platform-specific config pending).
Route Azure Pipelines builds through Chainsaw — pattern guidance (platform-specific config pending).

Troubleshooting

Troubleshooting CI/CD integration — authentication 401/400, org-slug URL mistakes, and policy-block 403 verdicts mapped to CHW-NNNN codes.

Config-as-code

Configure Chainsaw with YAML imports — declarative, version-controlled configuration.

Extend

Create custom hook scripts — add custom validation into the proxy pipeline.

Where to next

For signed events to external systems, see HMAC webhooks and SIEM export in Monitoring & Compliance.