Deployment analyzer in ReleaseOps

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 1 minute de lecture

    • The deployment analyzer reviews the update set in your release against rules to verify compliance with customizable rules.

    The deployment analyzer scans a given deployment request (and the update sets it contains) to check for changes as compared to the current state of the production instance (or the target release environment). To do, the deployment analyzer relies on rules and Automated Test Framework (ATF) code coverage. The deployment analyzer operates as a playbook activity, the results of which can be consumed to decide different actions in the deployment process.

    Deployment analyzer rules

    By default, the deployment analyzer has five rules. You can create rule types, definitions, and rules as needed. New rules appear in the playbook conditional setup automatically.

    For more information, see Deployment analyzer rules.

    Automated Test Framework (ATF) code coverage

    The deployment analyzer also leverages Automated Test Framework (ATF) code coverage to evaluate code changes prior to deploying the changes to the production (or target) instance. ATF code coverage is a tool that enables you to determine what percentage of code in a deployment request is covered by ATF test suites.

    By default, if ATF test suites cover less than 70 percent of the code in a deployment request, ReleaseOps transitions the deployment request to the Reconciling state and a test failure task is automatically created. You can adjust the ATF code coverage threshold in the deployment request assessment playbook. For more information, see .

    For more information about ATF code coverage, see ATF Code Coverage API.