Build Management Getting Started

Within the Zed Build application, it's easy to get started defining your new build. Use the New Build Wizard to quickly create a skeleton build that is tailored to your application, and then customize to your specifications using the Build Editor.

Prerequisites

Before you get into the New Build Wizard, ensure that you have at least one Product and Version defined in your system. The Build Definition will refer to these.

• Product List displays all products defined in your system.
• Product Edit displays a single product for editing.
• Version List displays all versions for each product in your system.
• Version Edit displays a single version definition for editing.

Build Wizard

The New Build Wizard will ask you a few questions in order to generate a build skeleton that matches your application as closely as possible.

Page One - Name And General Questions

On this screen, give your new build a name, and choose any of the options that pertain to your application.

Page Two - Product and Version

On this screen, choose the product and version that will be associated with this build. It is important to do this step for several reasons. First it will allow you to easily manage your build numbering scheme and keep it in sync with the product version that you are targeting. Second it will allow the build system to automatically update completed task assignments for tasks that have the same "Target Version" as the given build version.

Finish

After you have completed the information on the New Build Wizard pages, then finish the wizard and your new build will be saved and the Build Editor will be displayed to allow you to customize your build to your specifications.

Build Editor

The Build Editor is divided into multiple categories that allow you to fine tune the definition and execution of your automated build.

Main Page

The main page of the Build Editor allows you to edit the general properties of the build, as well as to define arrange and maintain the steps that make up your automated build.

See Build Editor for complete details on this page.

Environment Page

The environment page of the Build Editor allows you to define the exact environment setup that will be used for your automated build. This defines the build environment that will be used for each step that is executed, unless an individual step changes the environment definition for that step.

Version Control Page

The Version Control page of the Build Editor allows you to define the version control repositories that your build will access when checking out source code for the build to work on. This is also where you will set up any type of source control triggers that will launch builds when files in source control change.

Scheduling Page

The schedule page of the Build Editor allows you to define when your automated builds will be executed. You can also easily turn on and off automated execution without changing the schedule of your builds, simply by enabling or disabling the schedule.

Alerts On Success Page

The alerts on success page of the Build Editor allows you to define the settings for who the build system will notify when your automated build runs successfully. Alerts will be sent out if this e-mail is enabled, and they will be sent to the selected Users, Groups, and e-mail addresses.

Alerts On Failure Page

The alerts on success page of the Build Editor allows you to define the settings for who the build system will notify when your automated build runs but terminates abnormally with an error condition. Alerts will be sent out if this e-mail is enabled, and they will be sent to the selected Users, Groups, and e-mail addresses.

Build History Page

The build history page of the Build Editor allows you to see the saved history of executions of this automated build definition. Use the Scheduling page to configure how much history is kept, and use this page to browse through the output of builds that have executed.

This page also shows which executions of this build have been promoted to QA and Production.