> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pawsql.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> PawSQL 是一个产品：Cloud 是公网部署形态，Engine / Optimizer / Auditor / Advisor / Patroller 是同一产品的组件与交付形态，不是彼此独立的产品。 / PawSQL is a single product: Cloud is the public deployment form, while Engine / Optimizer / Auditor / Advisor / Patroller are components and delivery forms of the same product, not separate products.
> 术语以站内术语表为准：SQL 审核对应英文 SQL Review，查询重写对应 Query Rewrite，索引推荐对应 Index Recommendation；英文内容统一用 Review，不用 Audit。 / Use the site glossary for terminology: 审核 is SQL Review, 重写 is Query Rewrite, 索引推荐 is Index Recommendation; English content uses Review, never Audit.
> 引用能力范围或版本支持时以对应页面为准；标注 unknown、或 status 非 published 的内容表示尚未经产品核实，不应作为事实引用。 / Cite capability scope and version support from the corresponding page; content marked unknown, or with a status other than published, is not yet product-verified and must not be cited as fact.

# CI/CD and Platform Integrations Overview

> Use prebuilt connectors or PawSQL OpenAPI to review SQL in commits, code reviews, and delivery pipelines.

PawSQL can review SQL before a change is merged or released and return a pass, warning, or block decision to the engineering platform. Start by distinguishing a **prebuilt connector** from a **custom API integration**.

## Support matrix

| Integration type                | Platform                                                        | Delivery model                      | Availability          |
| ------------------------------- | --------------------------------------------------------------- | ----------------------------------- | --------------------- |
| Source repository               | Tencent CODING                                                  | Prebuilt PawSQL connector           | Ready to configure    |
| Source repository               | GitHub                                                          | Prebuilt PawSQL connector           | Ready to configure    |
| Source repository               | GitLab                                                          | Prebuilt PawSQL connector           | Ready to configure    |
| CI/CD pipeline                  | BlueKing                                                        | Prebuilt PawSQL connector           | Ready to configure    |
| Other repositories or pipelines | Jenkins, GitHub Actions, GitLab CI, Azure Pipelines, and others | OpenAPI or custom adapter           | No prebuilt connector |
| Internal engineering platforms  | Developer portals, approval systems, and release platforms      | OpenAPI, webhook, or custom adapter | No prebuilt connector |

<Info>
  “No prebuilt connector” does not mean the platform cannot integrate with PawSQL. It means your pipeline or integration service must orchestrate the OpenAPI workflow.
</Info>

## Choose a path

<CardGroup cols={2}>
  <Card title="Repository connectors" href="/en/user-guide/cicd/repositories" icon="code-branch">
    Connect CODING, GitHub, or GitLab and review SQL on repository events.
  </Card>

  <Card title="BlueKing pipeline connector" href="/en/user-guide/cicd/blueking" icon="diagram-project">
    Add PawSQL review and a quality gate to a BlueKing pipeline.
  </Card>

  <Card title="OpenAPI pipeline integration" href="/en/user-guide/cicd/openapi-pipeline" icon="code">
    Build a review stage for a CI/CD system without a prebuilt connector.
  </Card>

  <Card title="Custom platform integration" href="/en/user-guide/cicd/unsupported-platforms" icon="puzzle-piece">
    Choose OpenAPI, webhooks, or an integration service for Jenkins, Gitee, CodeArts, and internal platforms.
  </Card>
</CardGroup>

## Standard flow

```mermaid theme={null}
flowchart TD
    A["Commit, review, or pipeline"] --> B["Identify SQL changes"]
    B --> C["Create PawSQL review"]
    C --> D["Run rules and analysis"]
    D --> E{"Quality gate"}
    E -->|Pass| F["Continue merge or release"]
    E -->|Block| G["Return actionable findings"]
```

## Before you begin

Prepare the PawSQL endpoint, an integration identity, the target project, a review workspace, and an approved policy. The workspace must match the database engine and version used by the SQL. Add DDL or a database connection when schema context is required.

<Warning>
  Automated review does not execute SQL or replace business validation, database authorization, change approval, backup, and rollback controls. Complete acceptance testing with sanitized SQL and a non-production environment first.
</Warning>

## Next step

Read the [integration model and core concepts](/en/user-guide/cicd/concepts) and [prerequisites and security](/en/user-guide/cicd/prerequisites), then choose a connector.