/dynatrace-plugin

Plugin for Jenkins CI server that display data collected by the Dynatrace AppMon Test Automation features

Primary LanguageJava

Dynatrace AppMon Jenkins Plugin

This plugin for Jenkins pulls Test Automation data from Dynatrace AppMon and displays it through charts and tables on the project and build level.

Release 2.1.0 adds support for Jenkins Pipelines. Configuration and usage examples are described here.

Table of Contents

Installation

Using Jenkins Update Center

The recommended way of installing the plugin is by the Update Center (plugin directory). Navigate to Manage Jenkins -> Manage Plugins page and switch to the Available tab. Search for the "Dynatrace" keyword and install the plugin.

Manual Installation

This procedure is meant for developers who want to install locally built plugin version.

  • build the plugin from source using mvn package command
  • in Jenkins, go to Manage Jenkins -> Manage Plugins page
  • switch to the Advanced tab
  • upload the built plugin package from target/dynatrace-dashboard.hpi path in the Upload Plugin section
  • restart Jenkins when the installation is complete

Configuration

If you are using Jenkins 2.5 or higher, you need to enable the use of environment variables - see Jenkins 2.5+ build step execution failed with java.lang.NullPointerException

Global settings

The global settings for the plugin are located under Manage Jenkins -> Configure System -> Dynatrace Application Monitoring. The connection to the Dynatrace AppMon Server is configured in this section. The configured user needs to have the right credentials to be able to access the Test Automation REST API.

global settings

The advanced section enables you to set a delay before retrieving the test results from the server. Change this settings if you are not getting all the test results in Jenkins.

Build configuration

In the build configuration (<Project> -> Configure), first enable Use Dynatrace AppMon to monitor tests in the Build Environment tab and fill the required fields.

build environment

You can then choose one of two options to register Test Run:

  • Option 1, when:
    • you want an easy integration and don't want to adapt your build scripts too much
    • you are OK with defining the version in Jenkins to register the Test Run
  • Option 2, when:
    • you don't mind using an additional plug-in in your Ant/Maven scripts
    • you want to re-use the Ant/Maven version to register the Test Run

Post Build Action

At the end of the build, add the Dynatrace AppMon post-build action to retrieve the test results. You can also decide if the test results will change the build status.

post build action

Examples

Passing Test Run id registered from Jenkins to Maven

Registering Test Run using Dynatrace Maven plugin

Passing Test Run id registered from Jenkins to Ant

Registering Test Run using Dynatrace Ant plugin

Passing Test Run id registered from Jenkins to NAnt

Problems? Questions? Suggestions?

Additional Resources

Dynatrace AppMon Documentation

Recorded Webinar

Blogs