Quickstart guide
This article describes how to configure a Bitrise CI/CD workflow to automatically upload mobile app binaries to Data Theorem for scanning.
To automatically upload a mobile binary from Bitrise, a new step should be added at the end of your existing Bitrise workflow to upload the signed application binary (APK or IPA) to Data Theorem.
Step 1: retrieving the Upload API key
...
Step 3: creating a new Workflow step to upload builds
Add a new "Script" step at any point in your workflow after a signed IPA or APK has been generated:
.
Search for the Data Theorem Mobile Secure step
In the new "ScriptData Theorem Mobile Secure" step, insert the following code as the Script's content. This script assumes that the path to the signed APK path will be available in the BITRISE_SIGNED_APK_PATH environment variable (the default name used by the Bitrise "Sign APK" step). You might to update the name as needed.
...
| language | bash |
|---|
...
configure the step's inputs:
- The file path to your generated mobile app binary, for example it can be set to
$BITRISE_APK_PATHfor Android or $BITRISE_IPA_PATH for iOS
- Select your DT_UPLOAD_API_KEY secret variable set in step 2
Save the workflow and the integration should be ready. After configuring it, your workflow should like this:
Once the CI/CD uploads are enabled, pre-production scans will be completed automatically. Please note:
...