Build Management

A build is the application file (APK, IPA, or ZIP) uploaded to a RobusTest project. Builds are used as the target for test runs. You can upload, update, download, and delete builds via the API or through the project dashboard.

Uploading a Build

PUT /v3/project/:projectID/build?accesskey=<ACCESS_KEY>

Form Field	Description
`build`	The application file (APK, IPA, ZIP, AAB, or XCTest plan)
`buildInfo`	Optional JSON string with additional metadata

buildInfo fields:

Field	Description
`desc`	Description or build note (e.g. CI build number)
`label`	Display label for the build
`commitID`	Source control commit ID associated with this build
`buildCategories`	Array of category strings for organising builds

Example:

curl -X PUT \
  '<RobusTest URL>/v3/project/<PROJECT_ID>/build?accesskey=<ACCESS_KEY>' \
  -F 'build=@app-release.apk' \
  -F 'buildInfo={"desc":"Release candidate","commitID":"abc123"}'

The response includes the new build's id, which you pass to job creation as build.aut.

Listing Builds for a Project

GET /v3/project/:projectID/builds

Returns all builds uploaded to the project, sorted by upload date.

Getting Build Details

GET /v3/build/:id

Returns the build record including package name, version, size, and upload metadata.

Getting the Build Icon

GET /v3/build/:id/icon

Returns the app icon extracted from the build file.

Updating Build Metadata

You can update the label, description, or other metadata on an existing build without re-uploading the file.

PUT /v3/build/:id

{
  "label": "v2.4.1 Release",
  "desc": "Hotfix for login issue",
  "commitID": "def456",
  "buildCategories": ["release", "hotfix"]
}

Only the fields you provide will be updated.

Downloading a Build

Download a specific build:

GET /v3/download/build/:id

Download the latest build for a project:

GET /v3/project/:projectID/download/latestbuild

Deleting a Build

DELETE /v3/build/:id

Note: Deleting a build does not delete test results associated with it. Historical results remain accessible.

Reference Build (URL-based)

For builds hosted externally (e.g. on a CI artefact server), you can register a reference build using a URL instead of uploading the file:

POST /v3/project/:projectID/build/ref

{
  "remoteBuildUrl": "https://ci.example.com/artifacts/app-debug.apk",
  "label": "CI Build #142"
}

Project Dashboard