The Builds List
When you click Releases > Builds, you see a list of all builds in your project. The list shows:
Version - the software version (e.g., v2.14.1); click to view the build details
Environment - where the build was deployed (e.g., Production, Staging); shown as a colored tag
Release Date - when the build was deployed
Linked Release - which release this build belongs to; click to view release details
Added By - the user who created the build
Added - when the build was created in TestCollab
The list automatically refreshes every 15 seconds and paginates; you can choose to show 10, 20, 50, or 100 rows per page.
Filtering and Searching:
Use the Environment dropdown to filter by environment
Use the Version search box to find builds by version name
Use the Refresh button to manually reload the list
Creating a Build
Click the New Build button at the top of the Builds list.
Build Form Fields
The create build modal has the following fields:
Field | Required | Notes |
Version | Yes | The software version, e.g., |
Environment | No | Where the build was deployed; e.g., Production, Staging, Development. You can choose from common values or type a custom one. |
Release Date | No | The date the build was deployed. |
Release Notes URL | No | A full URL (must start with http:// or https://) linking to release notes or deployment documentation. |
Notes | No | Free-form text describing changes in this build. |
Filling in the Form
Enter a Version (required) - something your team uses to identify the build
Select or type an Environment
Set the Release Date using the calendar picker
Paste a Release Notes URL
Add Notes describing what changed
Click Add Build
Handling Duplicate Versions
If you enter a version and environment combination that already exists in your project, a confirmation dialog appears: "A build with this version already exists in this environment. Add anyway?"
This is not an error; it is intentional. The same version legitimately ships to different environments (e.g., v2.14.1 to Staging first, then to Production later). TestCollab allows it, but confirms you meant to do it. Click OK to add the duplicate or Cancel to go back and change the version.
Editing a Build
On the Builds list, click the Actions menu (three dots) next to a build and select Edit. You can modify any of the build fields (version, environment, release date, release notes URL, notes). Click Save when done.
Note: You can also edit the build's release assignment from the build detail page. See "Assigning or Changing the Release" in the Build Detail guide.
Deleting a Build
On the Builds list, click the Actions menu (three dots) next to a build and select
Delete.
Builds cannot be deleted if they are linked to test plans or have historical test results. If deletion is blocked, you'll see an error message like: "This build is linked to 3 test plans. Unlink those plans before deleting it." You'll need to remove the build link from each test plan first.
Notes on Permissions
Not everyone on your team can perform every action on builds. Permissions are based on your role in the project.
"Edit own" and "Delete own" means you can only modify builds that you created
If the "Edit" or "Delete" button is disabled, it shows a tooltip explaining why (e.g., "You can only edit builds you added")
Admins can do everything
If you need higher permissions to manage builds for your project, contact your project administrator.
Related Articles
Understanding Builds and Releases - Overview of the Builds and Releases feature
Creating Builds from Your CI/CD Pipeline - Automate build creation from your deployment pipelines
The Build Detail Page - View comprehensive testing results for a build