--- title: "Builds" slug: "builds" updated: 2026-05-08T09:41:24Z published: 2026-05-08T09:41:24Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Builds ## Overview Builds in the Deployment Server context represent a structured setup where customers can deploy, manage, and test their projects or designs across different environments. A Build acts as the central package for tracking, managing, reviewing, auditing, and shipping work across environments. This setup ensures that all necessary steps for transferring projects are handled efficiently and with confidence, minimizing risks during deployment. Each build is stored under a specific Deployment Package within an organization’s Deployment Folder, offering full traceability from development to production. Builds can be accessed through the Deployment Server UI by navigating to: **Organizations > Deployment Folder > Deployment Package**. --- ### Build Metadata Each build contains the following fields to support versioning, traceability, and quality control: | Field | Description | | --- | --- | | **Build ID** | A unique identifier automatically assigned to the build. | | **Project** | The name of the project the build belongs to. | | [**User Story**](/v9/docs/user-stories) | The specific user story associated with the build. | | **Unit Tests** | Status of unit test execution (with visual indicator). | | **QA** | Status of QA review and approval (with visual indicator). | | **Timestamp** | Date and time when the build was created. | --- ### Visual Representation of Build Accumulation The following screenshots illustrate how the system handles build accumulation for the same Project - User Story combination. In the example: - Build #1, Build #2, and Build #3 all belong to the same project and user story. - Build #3 includes: - All work from Build #1 and Build #2 - Plus any additional changes checked in since the previous builds The screenshots show how each build is versioned and how the latest build reflects a cumulative package of changes, ensuring consistency and completeness. This visual traceability allows teams to easily verify that no changes are lost or overwritten during the deployment lifecycle. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1760045376971.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1760045396211.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1760045407240.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1760045416095.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1760045427441.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1760045436900.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1760045447821.png) --- ### Unit Test Execution and Status Indicators When a user story is checked in from the Development Environment, if unit tests are included, they are executed automatically. The result of this execution is reflected visually in the Builds list. #### Unit Test Circle Indicators | Icon | Meaning | | --- | --- | | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1759965703165.png) | All unit tests passed successfully. | | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1759965788229.png) | One or more unit tests failed. | | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1760044162766.png) | No unit tests were included in the build. | These indicators are shown in the Unit Tests column for each build. --- ### Dev and Remote Unit Test Results Dashboard The **Dev and Remote Unit Test Results Dashboard** provides a build-level view of unit test results associated with a build. This dashboard centralizes test visibility by showing unit test outcomes that are captured as part of the build lifecycle. Unit test results can originate from two points in the workflow: - **Dev Unit Test Results:** During check-in, the **Run Unit Tests** option is enabled by default on the check-in dialog. This runs unit tests on the Development environment before check-in, and the results are synced to the Deployment Server as part of the build record. - **Remote Unit Test Results:** Results captured when unit tests are configured to run automatically in a target environment after deployment. To configure this, see [Deployment Types](https://documentation.decisions.com/docs/connecting-an-environment-to-deployment-server#deployment-types). When unit tests are run after deployment, the results are stored at the **build level**, allowing build records to include both development-side and target-environment test outcomes. This dashboard supports build validation by providing a single location to review unit test outcomes for the selected build, including tests executed in connected target environments. Note Remote unit test results are available when unit tests are configured to run after deployment. These results are captured as part of the selected build’s reporting details. --- ### Deploying Builds and QA Status Indicators #### **Deployment to QA** Builds can be deployed to the QA environment either manually or automatically. - **Manual:** Right-click the build and select **Deploy**. This triggers a change in the QA column status. - **Automatic:** Configure the QA environment to deploy a build as soon as it is created, eliminating manual deployment steps during continuous testing cycles. **Note:** Automatic deployment is restricted to **QA environments** and is not available in **Production**, ensuring controlled, safe releases. ![Auto deploy to QA configuration](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1772164455068.png) #### **Unit Test Execution on Target Environments** The Deployment Server can run unit tests in the selected target environment during deployment. This helps verify project integrity before changes are promoted. - **Manual:** Run unit tests during deployment. - **Automatic:** Configure the environment to run unit tests automatically on every deployment. #### **Deployment Wizard** Deploying a build opens the **Deployment Wizard**, which provides line-by-line visibility into each action performed during deployment to support review and troubleshooting. ![Deployment Wizard showing line-by-line deployment actions](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1772161907032.png) #### QA Circle Indicators | Icon | Meaning | | --- | --- | | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1760044834569.png) | Build is deployed to QA, awaiting review. | | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1759965703165.png) | Build approved by QA. | | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1759965766294.png) | Build rejected by QA. | QA reviewers can either approve or reject the build after review. Their decision updates the visual status and determines whether the build can progress toward final release. --- ### Deployment Package Readiness A Deployment Package becomes eligible to be marked as Ready only when the following conditions are met: 1. The final build for a Project - User Story has a **Green Unit Test Circle**, or no tests. 2. The final build for a Project - User Story has a **Green QA Circle** (approved by QA). 3. All user stories associated with the builds are in **Approved** status. This ensures that only validated and tested code, reviewed by both automation and QA, moves forward in the deployment lifecycle.