Help Center › User Guide › Interfaces and connectivity › Jenkins integration

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.

In this chapter

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:

The following overview appears:

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.

JUnit Plugin

Preinstalled. Optional. Allows Jenkins to output test results in a report in JUnit format. Required if you want to use the JUnit format for Ranorex Studio reports.