CircleCI

CircleCI lets teams build fully-automated pipelines, from testing to deployment.

Use the SEI CircleCI integration to integrate SEI with CircleCI.

Requirements

To use the CircleCI integration, you need a CircleCI Personal API token. Copy the token somewhere that you can retrieve it when you configure the integration. For instructions, go to the CircleCI documentation on Creating a personal API token.

Configure the integration on cloud

1. Select Integrations under Settings.

2. Select Available Integrations, locate the CircleCI integration, and select Install.

3. Configure the integration:

   • URL: Enter the URL for your CircleCI platform.

   • Authorization Token: Enter your CircleCI personal API token.

   • Repositories: You can specify repositories to associate with the integration. If unspecified, the integration associates all available repositories.

   • Fetch Action Logs: Select this option if you want SEI to ingest action logs from CircleCI.

   • Name: Enter a name for the integration.

   • Description, Tags, and Timezone are optional.

4. Once you have configured the integration, click Save

Configure the integration using satellite

The steps for configuring the integration using satellite is similar to configuring the integration on cloud, with the exception of using satellite to communicate with the Circle CI server.

Make sure to select the satellite integration checkbox while configuring the integration. Once you save the integration a satellite.yml file will be automatically generated and downloaded to your computer. Update it following the instructions here.

If you experience any issues while configuring the integration using the Ingestion Satellite, refer to the Ingestion Satellite Troubleshooting and FAQs.

Here’s a sample satellite.yml file:

satellite:
  tenant: <ACCOUNT_NAME>
  api_key: <SEI_API_KEY>
  url: 'https://staging.propelo.ai'
integrations:
  - id: '<INTEGRATION_ID>'
    application: circleci
    url: '<CIRCLECI_APP_URL>'
    apikey: <CIRCLECI_API_KEY>
    metadata:
      repos: <REPOSITORY>
      fetch_action_logs: true
      timezone: 'GMT-12:00'
      is_push_based: false