Set up a Version Control System Integration

For instructions on setting up the Version Control System of your choice, please expand the one desired below:

GitHub
With the Clubhouse GitHub integration, specially formatted commit messages can be used to link stories to commits, branches and pull requests, as well as move stories across your workflow. Following these instructions, you can configure the Clubhouse GitHub integration to work with one or more GitHub repositories.

 

Setting up the integration in Clubhouse

mceclip0.png
  1. In the Clubhouse app, click the User icon in the lower left corner, click Integrations, and then click GitHub.
  2. Click Add Account.

Setting up the integration in GitHub

 

Screen_Recording_2020-02-27_at_12.02.38.78_AM.gif


After clicking Add Account in Clubhouse, you will be taken to GitHub to select which GitHub account to link. From this next screen, you can authorize access to all repositories in the account, or only select repositories.

Once all or the select repos have been selected, click Install. You will be redirected back to Clubhouse to this message:

 

mceclip1.png

 

Connecting Individual Accounts

Individuals will need to ensure that their primary email address in GitHub is the same as one of their email addresses in Clubhouse. In GitHub, check your personal account settings, under the email tab.

GitHub_Primary_Email_Address.png
If this is not the same email address used to create your Clubhouse account, you'll need to add that email address to Clubhouse.

GitHub Event Handlers

To set up your integration to use our GitHub Event Handlers, follow these instructions. When you're done, make sure to check out our the guide to using our GitHub integration.
GitLab
With the Clubhouse GitLab integration you can link Stories to commits, branches and pull requests, as well as move Stories across your workflow. Following these instructions, you can configure the Clubhouse GitLab integration to work with your GitLab account.
Note: This integrates with GitLab.com and self-managed GitLab installations using version 9.5 or higher.
For self-managed GitLab users: Our GitLab integration needs to talk to the API of your self-managed GitLab install to properly process some event payloads. It determines the address of the API using the URLs included in the webhook payloads, and that address needs to be publicly accessible for us to reach it. Non-resolvable hostnames will cause the integration to not work correctly.

 

Setting up the integration in Clubhouse

Only Admins and Owners can activate this integration in Clubhouse. In the Clubhouse app, click the User icon in the upper right corner, click Integrations, and then click GitLab. Click the Slider to enable, then copy the GitLab Payload URL and open your GitLab account.
Clubhouse_GitLab_Integration_Enabled.png

In GitLab, choose specific Projects that you want to send data to Clubhouse, or if your GitLab.com plan supports Group Webhooks, you can send data from every Project in the Group. From the Project page (or Group page), click Settings > Integrations, then paste the GitLab Payload URL into the Integrations URL field.
Clubhouse_GitLab_Integration_Webhook_Setup.png
Next, check that the correct events will be sent to Clubhouse. Click the checkbox for:
  • Push Events
  • Comments
  • Merge request events
You may optionally include Confidential Comments.
_gitlab-testing___GitLab_2019-03-15_11-00-01.png
If you are not using GitLab's Group webhooks, be sure that you've added the GitLab Payload URL to the Integrations Settings for each Project that should send data to Clubhouse. Add user(s) email address as public in GitLab in order for Clubhouse's event handler to determine which GitLab user performed certain actions in Clubhouse, we match the email from GitLab payload to that of the Clubhouse user. Ensure that the public email in Settings (under user icon) > Main Settings is set to the appropriate email for the user in Clubhouse.
mceclip0.png
The last step is to place a personal access token from GitLab into Clubhouse. You may use an individual user's token, but it is recommended that you create a bot user in GitLab. 

 

1. Create a new user on your GitLab.com organization. Consider using a name that signifies this user connects GitLab to Clubhouse, like 'Clubhouse Bot'.

2. In GitLab, invite your bot user to the Projects that you want Clubhouse to access, and grant that user Developer permissions.

3. Log in with the bot user account and open the User Settings.

4. Generate a personal access token scoped to have API access  

 

Clubhouse_GitLab_Access_Token.png

 Clubhouse_GitLab_Access_Token_Generated.png

 

5. Copy the personal access token and paste it into the API Access Token field in the GitLab integration pane. Click Update API Access Token to save the token value.

Clubhouse_GitLab_Access_Token_added.png

BitBucket
With the Clubhouse Bitbucket integration, you can link Stories to commits, branches and pull requests, as well as move Stories across your workflow.Following these instructions, you can configure the Clubhouse Bitbucket integration to work with your Bitbucket Cloud account.
Note: This integrates with Bitbucket Cloud and not Bitbucket Server.

 

Setting up the integration in Clubhouse

Only Admins and Owners can activate this integration in Clubhouse. In the Clubhouse app, click the Gear icon in the upper right corner, click Integrations, and then click Bitbucket. Click the Slider to enable, then click Connect to Bitbucket.


Next, authorize the Bitbucket account you would like to connect to this Clubhouse Workspace.
Note: You can connect multiple Clubhouse Workspaces to the same Bitbucket account, but you cannot connect multiple Bitbucket accounts to the same Clubhouse Workspace.
When you’ve successfully authorized Clubhouse to access your Bitbucket account you’ll see which Bitbucket account Clubhouse is connected to in the integrations screen.