Skip to content

Commit 55f2651

Browse files
committed
Fix/docs review - addressing PR comments - 2
1 parent 637721a commit 55f2651

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/quality-gates/AssessmentOfTestResultsUsingQualityGates.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ How is status calculated:
7474
If you get this status, you can proceed with launch analysis (or choose another baseline) and rerun Quality Gates. For that check the section [How to recalculate Quality Gates](/quality-gates/AssessmentOfTestResultsUsingQualityGates#how-to-recalculate-quality-gates).
7575

7676
### Timeout
77-
Specially for integration with CI\CD, Quality Gates has parameter ```Timeout```. If a launch whose status should be sent to a pipeline, gets UNDEFINED status, the system uses a value from ```Timeout```. Default ```Timeout``` equals to 2 hours. It means, that after 2 hours after launch finish, the system force recalculates Quality Gate Status and defined status.
77+
Especially for integration with CI/CD, Quality Gates has parameter ```Timeout```. If a launch whose status should be sent to a pipeline, gets UNDEFINED status, the system uses a value from ```Timeout```. Default ```Timeout``` equals to 2 hours. It means, that after 2 hours after launch finish, the system forcibly recalculates Quality Gate Status and determines the status.
7878

7979
| Jenkins Job Status | Quality Gate Status | Description |
8080
| :----: | :----: | :--- |

0 commit comments

Comments
 (0)