Analyze build metrics with Insights to improve speed and efficiency: Use data from Bitrise Insights to track CI performance and test flakiness.
Bitrise uses API Token Based Auth, a developer-friendly delegated access protocol. Quolum has already connected the necessary wires with Bitrise. Using a sequence of click-throughs, your organization's administrator allows Quolum to make API calls to Bitrise without getting access to passwords.
Click the Connect button from the Connections card. If you are not an admin, you can invite your organization's Bitrise admin to make a connection to your Bitrise organization account. When you click on the Connect button, the web browser will navigate to the Bitrise login page.
Log in to Bitrise using your organization's credentials. The exact login mechanism may depend on your Bitrise plan, and the sign-in mechanism used. You may have corporate SSO such as Azure AD, GSuite, or Okta along with multi-factor authentication. Sometimes you may need to enter a Personal Access Token, the step by step details of which can be found at Bitrise API . Once you have successfully logged-in you can find the API Key and API Secret as mentioned below in Step 3.
The next screen after login into Bitrise is the consent screen. On this screen, Bitrise confirms whether you authorize Quolum to access your organization's data.
Once you have granted access to Quolum on Bitrise website, Bitrise is going to send you back to Quolum's page in Step 1, where you started. The Connect button on the Connections card would now say Reconnect. Reconnect is used to reauthenticate under circumstances where the access has expired.
Using the OAuth protocol, Quolum now has delegated access to your Bitrise Workspace. The Quolum server, running on Amazon AWS VPC, will be able to make API calls and retrieve feature-level utilization. Later, this data is crunched and available for visualization on the Quolum dashboard.
Updated 7 months ago