CircleCI Integration
Overview
GitAuto uses your CircleCI token to automatically read build logs when tests fail. This helps GitAuto understand what went wrong and generate fixes more accurately.
Why CircleCI Integration is Needed
When tests fail in CircleCI instead of GitHub Actions, GitAuto needs access to:
- Build logs showing test failure details
- Error messages and stack traces
- Test output and assertions
- Build environment information
Without CircleCI integration, GitAuto can only see that tests failed on GitHub, but cannot access the detailed logs from CircleCI to understand why they failed.
When to Use This
You should configure CircleCI integration if:
- Your repository uses CircleCI for CI/CD instead of GitHub Actions
- You want GitAuto to automatically fix test failures
- You need GitAuto to analyze build logs for better issue resolution
Note: If you use GitHub Actions, this integration is not needed as GitAuto can access those logs directly.
How to Configure
Step 1: Generate CircleCI Token
Visit CircleCI token settings and create a new Personal API Token.
Step 2: Configure in GitAuto
Go to CircleCI Integration Settings in GitAuto.
- Select your organization from the dropdown
- Paste your CircleCI Personal API Token
- Click Save
Step 3: Automatic Log Access
Once configured, GitAuto will automatically fetch CircleCI build logs whenever tests fail. The logs are used to understand the failure and generate appropriate fixes.
Token Permissions
Your CircleCI token needs the following permissions:
- Read access to project builds and logs
- Personal API Token type (not project-specific token)
Write permissions are not required as GitAuto only reads build logs.
Security
Your CircleCI token is stored securely in our database. GitAuto uses it only to read build logs when tests fail. The token is:
- Protected by database-level access controls
- Never exposed in logs or error messages
- Only accessible by your organization
- Used exclusively for reading CircleCI build logs
How It Works
- Test fails in CircleCI on your repository
- GitHub reports the failure to GitAuto via webhook
- GitAuto uses your CircleCI token to fetch the build logs
- GitAuto analyzes the logs to understand the failure
- GitAuto generates a fix and creates a pull request
Troubleshooting
GitAuto cannot access CircleCI logs
Verify that your CircleCI token is configured correctly and has not expired. Make sure the token has read access to all projects in your organization.
Token scope issues
Ensure your token is a Personal API Token with read access to builds. Project-specific tokens may not work for all repositories.
Need Help with CircleCI Integration?
Setting up CI/CD integrations can be tricky. If you're having trouble accessing CircleCI logs or configuring your token, we're here to help!
Contact us and we'll get your integration working smoothly.