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

# Set up a Bitrise connector

> C1 provides identity governance for Bitrise. Integrate your Bitrise instance with C1 for unified visibility and governance over user access.

## Capabilities

| Resource     | Sync                                                          | Provision |
| :----------- | :------------------------------------------------------------ | :-------- |
| Account      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Organization | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

**Additional functionality:**

*None.*

## Gather Bitrise configuration information

Configuring the connector requires you to pass in information from Bitrise. Gather these configuration details before you move on.

Here's the information you'll need:

* API Token

See the Bitrise docs for information on how to acquire credentials: [View the documentation](https://docs.bitrise.io/en/bitrise-ci/api/authenticating-with-the-bitrise-api.html)

This connector requires the following scopes:

* Workspace Role:Viewer
* Project Role:Admin

<Card title="Learn how to set the scopes" icon="book" horizontal href="https://docs.bitrise.io/en/bitrise-platform/workspaces/workspace-api-token.html#workspace-api-token" />

## Configure the Bitrise connector

<Warning>
  **To complete this task, you'll need:**

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Bitrise configuration information gathered by following the instructions above
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Bitrise** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Bitrise connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
        * Add the connector to a managed app (select from the list of existing managed apps)
        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.
        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Enter the configuration information from the previous section.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Bitrise connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Bitrise connector, hosted and run in your own environment.**

    When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

    ### Resources

    [Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector.

    ### Step 1: Set up a new Bitrise connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Bitrise connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
        * Add the connector to a managed app (select from the list of existing managed apps)
        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.
        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.
        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Bitrise connector deployment:

    #### Secrets configuration

    ```yaml theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-bitrise-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-bitrise-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>

      # Bitrise config
      BATON_BITRISE_API_TOKEN: <Bitrise API Token>
    ```

    See the connector's README or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-bitrise.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-bitrise
      labels:
        app: baton-bitrise
    spec:
      selector:
        matchLabels:
          app: baton-bitrise
      template:
        metadata:
          labels:
            app: baton-bitrise
            baton: true
            baton-app: bitrise
        spec:
          containers:
          - name: baton-bitrise
            image: ghcr.io/conductorone/baton-bitrise:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-bitrise
            envFrom:
            - secretRef:
                name: baton-bitrise-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Bitrise connector to. Bitrise data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

    **Done.** Your Bitrise connector is now pulling access data into C1.
  </Tab>
</Tabs>