...
Parameter | Description |
|---|---|
Name | Enter your preferred name of the rule. |
Webhook URL | Enter the Webhook URL. For Jenkins, refer to How to Construct Webhook URL? |
Query Params and Value | Enter the required Query Param and its value. e.g. TestCycleKey, TestCaseFolderId, TestCycleFolerId, etc. After adding the Query Params and Value, click on the Add button after entering Query Params and its Value. The entered details will be displayed below the fields. |
Headers and Value | Enter Headers and values e.g. “Authorization”. For Jenkins, refer to Authorization. After entering Headers and Values, click on the Add button after entering Header and its Value. The entered details will be displayed below the fields. → Mask Value After Saving: By default, the checkbox will be auto-selected if the system detects keywords such as “Authorization,” “Token,” “PAT,” or “API KEY” in the Header name. This smart detection mechanism helps identify critical or sensitive data and automatically protects the known sensitive parameters. Once a parameter is tagged with "Mask Value After Saving," its value will be displayed as asterisks after the creation of the CI/CD Rule. Note: Once a parameter value is set to be masked, the actual value becomes inaccessible after the initial save. You can only delete or overwrite it, as the system blocks any visibility into the existing secret value. |
HTTP-Method | Select the HTTP - method from POST/GET/PUT. For example, the remote build trigger API for Jenkins is “POST”. |
Webhook Body | Select from the options Raw/JSON/None on the drop-down and enter the Webhook Data or or request body in the field accordingly. → Mask Value After Saving: You can select or deselect the "Mask Value After Saving" checkbox when creating or editing Webhook Data. Once a parameter is tagged with "Mask Value After Saving," its value will be displayed as asterisks after the creation of the CI/CD Rule. Note: Once a parameter value is set to be masked, the actual value becomes inaccessible after the initial save. You can only delete or overwrite it, as the system blocks any visibility into the existing secret value. |
5. Click Create to save the configuration for Jenkins.
...
Once the rule is added, it is displayed on the Select CI/CD Rule panel of the test cycle detail page.
...
The same CI/CD Rule is also reflects reflected in the Automation module.
Once the CI/CD Rules are created either in the Automation module or in the Test Cycle module, you can view the summary of the configured rule in the panel.
...
The configuration details for the rule are displayed on the screen.
You can also make the required changes in the configuration from this screen.
...
You can disable the active CI/CD Rule from the Automation module. Once the rule is disabled, it can not be selected for triggering the build to the CI/CD tool from the Automation as well as the Test Cycle module. In the Automation module, the Trigger icon will not appear for the disabled/inactive rule. In the Test Cycle module, an error will be shown when you try to link a disabled/inactive rule with the test cycle.
...
You can delete a CI/CD Rule from the Automation module. If the rule is linked with any of the test cycles, then its all the references with the associated test cycle will be removed on deletion of the rule.
...