- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Quality Gates allows you to gate your workflows based on signals in Datadog. When creating a rule, you can define a rule scope, which states when the rule should be evaluated.
To filter rules that are evaluated for a specific CI pipeline, you can add a custom scope when creating a rule. This process requires you to use the --scope
option with the datadog-ci gate evaluate
command in your build configuration.
For example:
datadog-ci gate evaluate --scope team:backend --scope team:frontend
When the datadog-ci gate evaluate
command is invoked, the rules having a scope matching the command context are evaluated, and you can filter on rules that tag the backend
or frontend
teams.
For each scope (for example, branch
), you can select included or excluded values.
To create a rule that is evaluated in all branches except main
of the example-repository
repository, you can create a rule with the following scope.
Select when to evaluate
.example-repository
in the Repository field and click Include.main
in the Branch field and click Exclude.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.
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:
team
.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
.
Click Select when to evaluate
.
Enter example-repository
in the Repository field and click Include.
Click Add Filter and select Custom scope.
Enter a tag name and click Add Custom Scope.
Enter backend
in the team field and click Include.
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
.추가 유용한 문서, 링크 및 기사: