CircleCI
Connect
Connect CircleCI from the terminal. Pass --help for the flags CircleCI accepts.
polylane integration connect --type circleciA personal API token from User Settings → Personal API Tokens in CircleCI.
Connect one CircleCI organization with a personal API token.
- In CircleCI Personal API Tokens, create a personal API token. Project API tokens do not work.
- Paste the token into Polylane. Polylane checks it with CircleCI. If the token can reach more than one organization, select the organization to connect.
Read CircleCI pipelines, step logs, and test results, and request API changes through Polylane. Changes require safety review and approval.
Polylane maps your CircleCI projects into the context graph and watches workflow failure rates and durations on each project's default branch.
CircleCI personal API tokens have no scopes. A token can do what its owner can do in CircleCI. Polylane uses these CircleCI APIs:
| Tool | CircleCI API | What it unlocks |
|---|---|---|
circleciPipelines | API v2 pipelines, workflows, and jobs | Finds the latest pipelines of a project and the failed jobs of a workflow. |
circleciJobLogs | Job details and step output | Reads the output of the failed steps of a job. |
circleciTests | API v2 test metadata and flaky test insights | Reads the failed tests of a job and the flaky tests of a project. |
circleciApi | Any API v2 endpoint | Calls the CircleCI API; calls that change state, such as a rerun or a cancel, require safety review and approval. Environment variables, contexts, and checkout keys are not available. |
Disconnecting leaves the personal API token in CircleCI. Remove it under User Settings → Personal API Tokens in CircleCI.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Polylane held. Polylane removes what CircleCI's API lets it remove. The following stays until you remove it yourself:
- CircleCI personal API token
polylane integration disconnect <id>Tools
4Operations agents can perform in threads.