Jenkins Plugin Installation & User Guide

EOL Notice: The CA Agile Central plugin for Jenkins will no longer be enhanced or fixed and technical support will be discontinued effective June 2018. Existing customers can continue to use the integration, but we recommend using our new Build Connector for Jenkins. The new connector supports Pipeline jobs, has preview mode, provides log files, and is the version that we will continue to enhance.

The CA Agile Central plugin for Jenkins enables teams to use CA Agile Central to see the build status for the projects they are working on, display charts on build health, and trace code commits to builds. The plugin achieves this by populating build data into CA Agile Central.

When used in conjunction with a Version Control System (VCS) and a CA Agile Central VCS connector, the Jenkins plugin will link Builds to ChangeSets as well. The CA Agile Central VCS connector will parse the commit message, and if CA Agile Central artifacts are mentioned (such as DE27), the VCS connector will link the artifact to the ChangeSet for the change committed to the SCM system. When the next Jenkins build occurs, the Jenkins plugin will link the ChangeSet to the Build in CA Agile Central. The result is traceability from Story/ Defect to ChangeSet to Build.

Additionally, custom dashboards can be built to display Build Health and Traceability apps to manage the health of continuous build/test pipelines across the enterprise.

This install guide includes:

Software Requirements

The following sections describe the software requirements.

Jenkins Support

  • We currently support Jenkins 2.7.1. (Due to a defect in Jenkins versions 1.598 to 1.609, these versions cannot be used with this plugin on any of the platforms listed below.)
  • Testing has been done on Ubuntu, CentOS, Mac OS X, and Windows Server 2012. These operating systems are recommended.

SCM System Support

  • SCM systems are necessary in order to link ChangeSets to Build objects in CA Agile Central so that Stories/Defects can be traced to Builds.
  • Certified to support Git, Subversion, and Mercurial.
  • A Jenkins plugin for the SCM system must be installed in Jenkins. Jenkins has a built-in Subversion plugin, and optional plugins for Git and Mercurial are available on the Jenkins CI site.
  • The CA Agile Central VCS connector for the appropriate SCM must be installed in order for ChangeSets to be populated in CA Agile Central (Git, Subversion, Mercurial).
  • NOTE*** The Jenkins plugin does not support SSO at this time

Connector Download

To download the connector, follow the steps here.


Installation of the plugin follows these basic steps:
  1. Install the Ruby Runtime plugin into Jenkins (one time)
  2. Install the CA Agile Central Build Notifier plugin into Jenkins (one time)
  3. Configure the plugin’s global settings (one time)
  4. Configure a Jenkins job to publish build results into CA Agile Central (for each job)

Set up CA Agile Central

Verify that your target Workspace Configuration object has BuildandChangsetEnabled set to true.

Your CA Agile Central workspace administrator needs to enable this for your target workspace. If it is not enabled, the connector will work, but you will not be able to see any of the changeset/change information that is associated with your Rally work items (story, defect, task ).

The workspace administrator must edit the workspace and do the following:
  1. Select the Setup icon .
  2. Select the Workspaces & Projects tab .
  3. On the Workspaces & Projects summary page , select your workspace.
  4. From the Actions drop-down, select Edit.
  5. On the workspace editor, select the checkbox labeled Enable Build and changeset.
  6. Select Save & Close.

Jenkins Setup

If you are unfamiliar with Jenkins plugins, consult the Jenkins documentation for plugins to become familiar with the concept and how to install plugins in Jenkins.

Upgrading the Plugin from a Prior Version to the 4.0.1 Version

If you were using the Jenkins plugin for CA Agile Central v4.0.0 or below, you should follow these steps before installing v4.0.1 of the Jenkins plugin:
  1. Make a note of all of your Jenkins settings, at both the global and job levels. You will need to re-enter these after installing the new plugin.
  2. Uninstall the CA Agile Central plugin for Jenkins (Or Rally plugin) from Jenkins
  3. Follow the instructions below to install the plugin into Jenkins

Installing the Plugin into Jenkins on Linux, Mac OS X, and Windows Server 2012

This is also found on the README that comes with the plugin.

You may need to restart Jenkins.

Follow these steps:
  1. In the Jenkins interface, navigate to Manage Jenkins, Manage Plugins.
  2. Select the Advanced tab.
  3. In the Upload Plugin section, select Choose File, and select ruby-runtime-plugin-0.14.hpi.
  4. Select Upload. Jenkins displays a status screen that shows the plugin installing.
  5. Install the Jenkins CA Agile Central Publisher plugin following the same steps as above.
  6. Navigate to the Manage Plugins screen and select the Advanced tab.
  7. In the Upload Plugin section, select Choose File, then select the agile-central-build-publisher-1.0.1.hpi. Jenkins displays a status screen, which shows the plugin installing.
Note: The order of steps is important. If agile-central-build-publisher is uploaded prior to ruby-runtime-plugin, Jenkins will automatically install the 0.12 version of ruby-runtime plugin instead of the necessary 0.14 version. Our plugin will not work with the publicly available 0.12 version (ruby-runtime-plugin-0.12.hpi) or 0.13 previously packaged by CA Technologies.


Once the plugin is installed, it needs to be configured at the global level, as well as once for each Jenkins job.

Configuring Global Settings

Follow these steps:
  1. In the Jenkins web interface, go to Manage Jenkins, System Configuration.
  2. In the CA Agile Central Build Publisher section, complete the following fields:
    • CA Agile Central Server: Enter in the text box. If you are evaluating CA Agile Central, enter If you are running an On-Premises instance, enter the name of your CA Agile Central server.
    • CA Agile Central Username and CA Agile Central Password: The username and password for a CA Agile Central user with access to the workspace in which you want to publish Jenkins build results.
  3. If you access CA Agile Central through a proxy server, select Advanced in the CA Agile Central Build Publisher Proxy Settings section to display the fields used to specify the proxy:
    • Proxy Server: the name or the IP address of the proxy server
    • Proxy Port: The port number to use on the proxy server
    • Proxy Username (optional): A valid username for the proxy server, if it requires authentication
    • Proxy Password (optional): A valid password for the proxy server, if it requires authentication

Configuring a Jenkins Job to Publish Build Results

Any free-style or maven2 job in Jenkins can be configured to publish a BuildDefinition & Build in CA Agile Central. Every project in CA Agile Central has one or more BuildDefinitions that can be used to publish a build status indicator.

In Jenkins:
  1. Go to the Jenkins job you want to configure to publish build results to CA Agile Central, then select Configure in the upper-left.
  2. In the Post-build Actions section of the page select the Add post-build action drop-down and select the CA Agile Central Build Publisher option.
  3. In the CA Agile Central Build Publisher section of the page, enter the name of the CA Agile Central workspace and project in which the build results are to be published ( note that the user you entered in the global config must have permissions to the workspace you specify). Known issue: If publishing to a sub project the top level project will be entered for project. The plugin will display the following error if sub project is referenced: ERROR: [Rally Publisher] Unable to post Build info to Rally for Test1 build #35, unable to find default project SubProj1
  4. Select Save on the configuration page.

The next time the job runs, the plugin will search for a BuildDefinition in CA Agile Central with the same name as the Jenkins job. If it is not found, one will be created. Each time the job runs, a Build object will be created in CA Agile Central and linked to this BuildDefinition.

Repeat these steps as necessary to configure additional Jenkins jobs to publish results to other CA Agile Central projects.

Viewing Build Information in CA Agile Central

You can view build information in reports or custom dashboards.

Viewing Build Health in Reports

Build health reports are available in the Reports → Reports page in Rally. Specifically, Build Health and Build Health by Iteration are available.

Creating Custom Build Dashboards

When building custom dashboards, you can select different Build dashboard apps, including Build Health and Build Health by Iteration.


Use the following command to start Jenkins in debug mode and view messages:

java  -Drally.debug="true"  -jar  jenkins.war  --httpPort=9000

Console Output

If you are having trouble with the plugin, view the console output from your job or the application server log that is running Jenkins. To view the console output from the job, select a build number in the Jenkins web interface, then select Console Output on the resulting Jenkins page.

Tomcat Server Log

If you are using Tomcat, navigate to [TOMCAT_INSTALL_DIR]/logs/catalina.out to view the application server log.

Password Changes

Ensure that the CA Agile Central Username and Password entered into the Global Configuration for the plugin are correct and haven’t changed.

Object Model

Once the Jenkins plugin for CA Agile Central has run, the relationship between the data objects inside CA Agile Central is the following:

Historical Version Highlights

  • Context identification parameter added.
  • Global settings retained and available restarting Hudson.
  • Support of BuildDefinition and Build objects in Rally.
  • Support for Hudson versions through 1.381.
  • Support for Maven2 project types in Hudson.
  • Support for Git and Perforce as SCM options.
  • Proxy settings for Rally are persisted
  • Duration field in Build objects populated with Jenkins provided value.
  • Added debug flag.

Supported Versions

Version End of Support
Jenkins 2.x and later N/A
Jenkins 1.642.4 to 1.651.2 12/1/2016
Jenkins 1.42 to 1.642.3 12/1/2016
Jenkins 1.41 and below; any Hudson version 4/1/2013

Revision History

  • 4.0.1 18-May-2016
    • Fixes:
      • SSL error connecting to Agile Central caused by older ruby-runtime-plugin.
  • 4.0.0 16-November-2015
    • Enhancements:
      • Brand redesign.
  • 3.0.6 25-February-2015
    • Known issues:
      • The following error is received when entering sub project in Build Configuration:

        ERROR: [Rally Publisher] Unable to post Build info to Rally for Test1 build #35, unable to find default project SubProj1

      • Plugin does not translate Chinese characters for Project name correctly.

Version History

Version Notes Files Date
  • Fix abort due to SSL failure
Jenkins Plugin 4.0.1 5/18/2016
  • Brand redesign
Jenkins Plugin 4.0.0 11/16/2015
  • Rebuilt with new architecture
  • Fixes defect: special characters and trailing spaces in project names
Jenkins Plugin 3.0.6 1/28/2015
1.0 - 2.4.1 Unsupported N/A


Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.