Enterprise Release Management

The ServiceNow® Enterprise Release Management application can be used to efficiently plan and manage enterprise releases, product releases, and the deployment process.

You can:
  • manage the phase gate process; define the key aspects of an enterprise release, and plan the release activities in phases.
  • manage the marketing aspects of a release: Market release date, features developed in a release, and so on.
  • define the key aspects of a product release, maintain different versions of product releases, by that, track features released in each product version.
  • define a deployment pipeline for product builds. You can:
    • track the entry of builds in appropriate deployment phases (environments).
    • create and execute test plans to check for any failures in builds.
    • validate builds and complete build approvals.
Table 1. States of a build
State Description
Entering Phase When a build enters the first phase, the state of the build is set to Entering Phase. This state is meant to be used as a signal either through a custom business rule or as a way to query new builds for automated systems to know when an action must be taken.
Verification Pending Once tasks in entering phase are complete, the state of the build must be set to Verification Pending.
Verification Complete Once all the tests pass, deployment tasks are in the closed complete state, and approvals are done, the state of the build is automatically set to Verification Complete. This state is a signal for automation tools to perform any exiting phase tasks.
Exiting Phase Once verification tasks are complete, the state of the build must be set to Exiting Phase. In this state, the build is automatically moved to the next deployment phase defined by the Order field.
Figure 1. How does a build transit from one state to another
Illustration depicting the transition of a build from one state to another