Install and configure plugins

Jenkins uses plugins to integrate functionality of other applications. To integrate Ranorex Studio tests in Jenkins, a series of plugins is required. Other optional plugins add additional functionality. Some of these plugins normally come preinstalled and activated on a Jenkins server, others have to be downloaded and activated.

On this page, we list the the required and optional plugins and what configurations you need to make in Jenkins for them to work correctly for the Ranorex Studio integration.

Access plugins

For detailed information on downloading and installing plugins, please refer to this article in the official Jenkins documentation.

To access plugins in Jenkins:

Click Manage Jenkins.

Click Manage Plugins.

The filter allows you to search for plugins

Required and optional plugins

Ranorex Test Execution Plugin

Must be downloaded and installed so Jenkins can process Ranorex Studio tests.

MSBuild Plugin

Must be downloaded and installed so Jenkins can compile and build the Ranorex Studio solution.

GitHub Plugin

Preinstalled. Optional. Allows Jenkins to access GitHub repositories. We need it because we use GitHub; if you use a different provider, a different plugin may be required.

GitHub Plugin

Preinstalled. Optional. Allows Jenkins to access GitHub repositories. We need it because we use GitHub; if you use a different provider, a different plugin may be required.

Configure plugins

Some of the plugins require that you make some configurations before they will work correctly for the Ranorex Studio integration.

Configure Ranorex Test Execution Plugin

Click Manage Jenkins.

Click Configure System.

Under Ranorex Integration, check the option Summarize arguments in Console output.

Click Save.

Configure MSBuild Plugin

Click Manage Jenkins.

Click Global Tool Configuration.

Click Add MSBuild.

Enter a sensible name for the build.

Enter the path to your local .NET installation.

Click Save.