Select the policy that you want this gate to enforce. You can create more policies in DevOps Insights.

Select a toolchain. If you have not created a toolchain yet, create one here.

Enter the name of the build job that triggers this test job. You can use an environment variable, such as $BUILD_JOB.

Select an API Key from the menu. If no API Key are in the menu, click Add to add one. Click Test Connection to verify the selected credentials. The use of Username/Password will be deprecated soon

Select this check box to cancel associated Jenkins builds when this gate fails.

Select this check box if the deployed app is not built in Jenkins.

Type a name for the application that information is being uploaded for. Use this application name when you configure DevOps Insights gates. You can use an environment variable, such as $APP_NAME.

Select this check box if you want to set your own build number.

Type a name for the application that information is being uploaded for. Use this application name when you configure DevOps Insights gates. You can use an environment variable, such as $APP_NAME.

Select an API Key from the menu. If no API Key are in the menu, click Add to add one. Click Test Connection to verify the selected credentials. The use of Username/Password will be deprecated soon

Type the ID of your toolchain. If you have not created a toolchain yet, create one here.

Type the ID of your toolchain. If you have not created a toolchain yet, create one here.

Enter the name of the build job that triggers this test job. You can use an environment variable, such as $BUILD_JOB.

Type the name of the environment that this job deploys to. If this environment is your staging environment, type "STAGING." If this environment is your production requirement, type "PRODUCTION." If you do not specify staging and production environments, DevOps Insights cannot completely analyze your project.

Select an API Key from the menu. If no API Key are in the menu, click Add to add one. Click Test Connection to verify the selected credentials. The use of Username/Password will be deprecated soon

Optional: If this is a web application, enter its URL. You can use an environment variable, such as $APP_URL.

Select this check box if you want to set your own build number

Type a name for the application that information is being uploaded for. Use this application name when you configure DevOps Insights gates. You can use an environment variable, such as $APP_NAME.

Select an API Key from the menu. If no API Key are in the menu, click Add to add one. Click Test Connection to verify the selected credentials. The use of Username/Password will be deprecated soon

Select a toolchain. If you have not created a toolchain yet, create one here.

Enter the name of the build job that triggers this test job. You can use an environment variable, such as $BUILD_JOB.

Type the hostname of the server that your SonarQube instance runs on. Do not enter a trailing slash.

Enter your API token that SonarQube generated for you.

Type the key of the SonarQube project that you wish to scan.

Select this check box if you want to set your own build number

Type a name for the application that information is being uploaded for. Use this application name when you configure DevOps Insights gates. You can use an environment variable, such as $APP_NAME.

Select the type of test. Your tests must correspond to rules in policies.

Supported formats:
• Code coverage: Istanbul, BlanketJS
• Unit and functional verification tests: Mocha, xUnit, and Karma Mocha

Enter the test result file location relative to the root directory. The result file must contain results in the format that you selected for the metric type. This field supports wildcards and environment variables. If you leave this field empty, DevOps Insights generates a simple test report that is based on job status. Mocha, KarmaMocha, Istanbul, and BlanketJS test results must be in the JSON format. xUnit test results must be in the XML format.

Select a toolchain. If you have not created a toolchain yet, create one here.

Enter the name of the build job that triggers this test job. You can use an environment variable, such as $BUILD_JOB.

Select an API Key from the menu. If no API Key are in the menu, click Add to add one. Click Test Connection to verify the selected credentials. The use of Username/Password will be deprecated soon

Optional: You can upload another test result file and select another metric type in this job.

Select this check box if you want to set your own build number

Type a name for the application that information is being uploaded for. Use this application name when you configure DevOps Insights gates. You can use an environment variable, such as $APP_NAME.