Capabilities

• Sync team members from Buildkite to ConductorOne

• Resources supported:

  • Teams

Add a new Buildkite connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

1. In ConductorOne, click Connectors > Add connector.

2. Search for Buildkite and click Add.

3. Choose how to set up the new Buildkite 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 ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

   Do you SSO into Buildkite using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged Buildkite app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   A Buildkite connector owner must have the following permissions:

   • Connector Administrator or Super Administrator role in ConductorOne
   • Team with read membership access in Buildkite

5. Click Next.

Next steps

• If you are the connector owner, proceed to Configure your Buildkite connector for instructions on integrating Buildkite with ConductorOne.

• If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your Buildkite connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and Team with read membership access in Buildkite must perform this task.

ConductorOne uses personal API access tokens to manage access.

Step 1: Create a new API access token

1. In Buildkite, select your Account Name and click Personal Settings.

   

2. On the left sidebar, select API Access Tokens.

   

3. Click New API Access Token.

   

4. Name your token ConductorOne Integration and select the following permissions:

   • Organization Access: your org name
   • Read Teams
   • Read Organizations
   • Read User
   • GraphQL API: Enable GraphQL API Access

5. Click Create New API Access Token and copy the token. We’ll use it in Step 2.

Step 2: Add your Buildkite credentials to ConductorOne

1. In ConductorOne, navigate to the Buildkite connector by either:

   • Clicking the Set up connector link in the email you received about configuring the connector.

   • Navigate to Connectors > Buildkite (if there is more than one Buildkite listed, click the one with your name listed as owner and the status Not connected).

2. Find the Settings area of the page and click Edit.

3. Paste the API access token you generated in Step 1 into the API token field.

4. Click Save.

5. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Step 3: Select an organization

1. On the Buildkite integration page, click Edit in the Organization section.

2. Wait for the UI to populate a list of organizations your API access token has access to, then select the appropriate organization.

   

3. Click Add Organization to save the selected organization and then click Save.

That’s it! Your Buildkite connector is now pulling access data into ConductorOne.

Configure the Buildkite integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between Buildkite and ConductorOne.

See the ConductorOne Buildkite integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.