Create a build Create a build record using the Build form. You can also use the information on the Builds page to create a report. Before you beginRole required: Deployment Pipeline Manager [sn_erm.deployment_pipeline_manager] Procedure Navigate to Enterprise Release Management > Deployment Management > Builds. Note: You can also create builds from Builds related list in the Deployment Phase form. Click New. On the Build form, fill in the fields. Field Description Number System generated number with a configurable prefix. Build ID Unique identifier of the build. Branch label Label name of the branch where the code is committed. Branch label is human readable as well as machine readable. Commit (Optional) Code commit for which the build is generated. Deployment phase Deployment phase (environment) indicating the entry of a build. State State of the build. When a build enters a particular phase in a deployment pipeline, it moves to the Entering Phase state. For example, activities in this state could be deploying code or building business rules that act on the build when it enters a deployment phase. Once all the activities in the Entering Phase state are complete, build moves to the Verification Pending state, where: Each deployment task template creates a deployment task. Test plans related to deployment phase are set to the In Progress state. Build approval request is sent to all the members of the approval group. Once all the activities in the Verification Pending state are complete, the build moves to the Verification In Progress state. When all test cases in the test plans are passed, all deployment tasks are Closed Complete, and the deployment approval is Approved, the build moves to the Verification Complete state. In the Verification Complete state, activity such as cleaning the environment is done. Once all the activities in the Verification Complete state are complete, the build moves to the Exiting Phase state. At this point, change the reference of the deployment phase to the next phase based on the order in the deployment pipeline. When any one of the test cases in the test plans is set to failed or any deployment task is marked Closed Incomplete or Closed Cancelled or the deployment approval is Rejected, the build moves to the Verification Failed state. When any of the build activities are kept on hold, the build moves to the Verification On Hold state. Configuration item Reference to the Configuration Item managed by Configuration Management Database. Branch ID Unique identifier of the branch where the code is committed. Branch ID is machine readable. Build reference Reference or source from where the build can be downloaded. Click Submit. What to do nextUse the following related lists:Table 1. Build related lists Related list Description Build Phases Indicates the deployment phase in which a build has entered. Build test plans When the state of the build is Verification Pending, test plans are pulled from deployment phase into the build. To add a new test plan, click New. Build tasks When the state of the build is Verification Pending, build tasks are automatically created from the deployment task templates. To add a new build task, click New. Build Approvals When the state of the build is Verification Pending, approvers are added to the Build approvers list based on assignment group selected in a deployment phase. To approve a build, click New.