Set up Quality Gate Rules

Quality Gates is not available in the selected site () at this time.

Join the Beta!

Quality Gates is in public beta.


Generally, to set up Quality Gates:

  1. Create one or more rules on the Datadog site.
  2. Invoke Quality Gates by using the datadog-ci gate evaluate command in your CI pipeline.

Create a rule

To create Quality Gates rules for your organization, your user account must have the quality_gate_rules_write permission.

  1. In Datadog, navigate to CI > Quality Gate Rules and click + New Rule.
  2. Define the rule scope. The rule scope defines when the rule should be evaluated. For example, you can create a rule that it is evaluated only on specific repositories and branches. To define the scope for a rule, switch to select when to evaluate and add included or excluded values for the scope. See rule scopes for more information.
  3. Select the rule type. You can choose between Static Analysis and Test.
  4. Define the rule condition. The rule condition states in which scenario the rule fails, failing the related pipeline (if the rule is blocking). You can select one of the existing rule conditions for the rule type you have selected.

The following example shows how to create a static analysis rule that fails when there are one or more static analysis violations with “error” status and “security” category being introduced in a specific commit:

Rule for static analysis security errors
  1. Select whether the rule should block the pipeline when it fails. Non-blocking rules are helpful when you roll out a new rule and want to verify its behavior before making it blocking.
  2. Select the time window over which the query is evaluated.
  3. Specify a rule name that describes the rule that you are creating.
  4. Click Save Rule.

Invoking quality gates

Quality Gates requires datadog-ci version 2.27.0 or later.

Invoke the Quality Gates evaluation by calling the datadog-ci gate evaluate command.

This command:

  1. Retrieves all the rules that have rule scopes and custom scopes that match the current pipeline context (repository, branch, or custom scope passed in the command).
  2. Evaluates all the matching rules.
  3. Fails if one or more blocking rules fail, thereby blocking the pipeline.
For the command to work properly, it's important that the events (tests, static analysis violations) are sent to Datadog before the datadog-ci gate evaluate command is executed. Otherwise, the rules might have an incorrect behavior due to the absence of the events.
Environment VariablesDescription
DD_API_KEYPoint to your Datadog API key.
DD_APP_KEYPoint to your Datadog application key.
DD_SITE(Optional) Point to a specific Datadog site (default value is

For example:

DD_SITE= DD_API_KEY=API_KEY DD_APP_KEY=APP_KEY datadog-ci gate evaluate

Configure the behavior of the datadog-ci gate evaluate command using the following flags:

  • --fail-on-empty: The command fails if no matching rules are found. based on the current pipeline context. By default, the command succeeds.
  • --fail-if-unavailable: The command fails if one or more rules cannot be evaluated because of an internal issue. By default, the command succeeds.
  • --timeout: The command stops its execution after the specified timeout in seconds. The default timeout is 10 minutes. The command typically completes within a few minutes, but it could take longer.
  • --no-wait: Skips the default time that the command waits for the events (for example, tests, static analysis violations) to arrive to Datadog. The default wait time makes sure that the events are queryable in Datadog before the rules are executed, avoiding incorrect evaluations. If, in your pipeline, the job containing the datadog-ci gate evaluate command is called several minutes after the related events are sent to Datadog, you can opt to skip this waiting time by specifying the --no-wait flag. However, if used incorrectly, this flag may result in inaccurate rule evaluations.

Add custom scopes to the command by using the --scope option one or more times:

datadog-ci gate evaluate --scope team:backend --scope team:frontend

Check the command logs to see the overall gate evaluation status and information about the rules that were evaluated.

Datadog-ci gate evaluate logs

Rule scope

Quality Gates allows you to gate your workflows based on signals in Datadog. You can create two types of rules: Static Analysis and Tests. For example, you can block code from being merged if it introduces new flaky tests, code security violations, or other issues that wouldn’t normally fail your CI/CD pipelines and end up deployed to production.

When creating a rule, you can define a scope, which states when the rule should be evaluated. If the rule scope is set to always evaluate, the rule is evaluated on all repositories and branches. With Quality Gates, you have control over what is merged into the default branch, and ultimately on what is deployed. This allows you to ensure that the code running in production is meeting high quality standards, reducing incidents, and minimizing unwanted behaviors.

Rule scope for rules always evaluated

When the datadog-ci gate evaluate command is invoked, the rules having a scope matching the command context are evaluated.

For each scope (for example, branch), you can select included or excluded values. When included values are selected, the rule is evaluated if one or more included values are part of the command context.

When excluded values are selected, the rule is not evaluated if any of the excluded values are part of the command context.

Create rules

For example, to create a rule that is evaluated in all branches except main of the example-repository repository, define the following scope:

Rule scope for example-repository and not main branch

If a rule does not contain a scope, it is evaluated for all values for that scope. For example, if a rule does not contain the repository scope, it is evaluated for all repositories.

Custom scope

In addition to branch and repository, you can define custom scopes to filter rules that are evaluated for a specific CI pipeline.

To add a custom scope when creating a rule:

  1. Click + Add Filter and select Custom Scope.
  2. Define the scope name, for example, team.
  3. Define the scope’s included or excluded values.

Unlike the branch and repository scopes, custom scopes must be passed to the datadog-ci gate evaluate command using the --scope option. For example, you can create a rule that is evaluated for the example-repository repository, but only when the team is backend:

Rule scope for example-repository and team backend

The rule is evaluated when the following command is invoked in a CI pipeline of the example-repository repository:

  • datadog-ci gate evaluate --scope team:backend

The rule is not evaluated when the following commands are invoked instead:

  • datadog-ci gate evaluate, which does not specify any team.
  • datadog-ci gate evaluate --scope team:api --scope team:frontend, which specifies teams other than backend.

Manage rules

To edit a Quality Gates rule, click the Edit icon to the right of the Creator avatar on the Quality Gates Rules page.

Edit a Quality Gates rule

To delete a Quality Gates rule, click the Delete icon next to the Edit button on the Quality Gates Rules page. Alternatively, you can edit the rule and click Delete Rule.

Delete a Quality Gates rule

Enable GitHub check creation

You can automatically create a GitHub check for each rule evaluated. When this feature is enabled, the evaluation results appear directly in GitHub. The check contains additional information about the rule evaluation, such as the failure reason and the matching events in Datadog.

To enable GitHub Checks:

  1. Go to the GitHub integration tile. If you do not have this integration set up, or you don’t have a GitHub app within the integration, follow the GitHub integration documentation to set one up.
  2. Grant Checks: Write access to the GitHub application.

After the permission is granted, you can see the checks in GitHub.

Note: Re-running a check does not re-run the corresponding Quality Gates rule.


Only users with the quality_gate_rules_write permission can create and edit Quality Gate rules. Users with the quality_gate_rules_read permission can view Quality Gate rules.

For more information, see the RBAC Permissions documentation.

Further reading

Additional helpful documentation, links, and articles: