Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata


Deprecated since core 1.480.3.  Use Team Concert Plugin instead.  This plugin integrates IBM's Rational Team Concert (RTC) source control to Hudson.

Plugin Information

No information for the plugin 'rtc' is available. It may have been removed from distribution.

This plugin uses the RTC's command line interface, scm (or lscm), to issue commands to the RTC Server.

At the moment, this plugin supports:

  • Loading a workspace (checkout in RTC's lingo).
  • Polling a RTC Stream to automatically accept changes and start builds.
  • Links from the Hudson change sets to Jazz Team Server Web Access. (Also known as a repository browser)



The plugin requires that the SCM command line tool from Rational Team Concert is installed and findable in the path of the server.

System configuration

There will be a new "Rational Team Concert" section where you can configure the executable name.

This is the command line tool that will be invoked. It's advised to use lscm (lscm.bat for Windows servers) instead of the default scm, because the former uses less system resources.

Job configuration

In your Job configuration, select RTC as your Source Code Management option and fill the required fields:

Username and password are not required if you previously issued the following command in your system:

scm login -r https://yourrepository/address -u username -c

It's recommended to have a username and workspace dedicated to Jenkins.


Version 0.3 (Dec 12 2011)

* Passwords are now hidden (in job configuration screen and config.xml)

* Now works on master/slave environment

* Some internal changes to support a future plugin to integrate with RTC's build system

Version 0.2.2 (Nov 29 2011)

* Fixed timeout issue with large workspaces

* Initial support for chinese version of 'scm' (not fully tested yet)

Version 0.2.1 (Nov 16 2011)

* Fixed compatibility with older 'scm' versions

Version 0.2 (Nov 14 2011)

* Fixed compatibility with Unix systems

* Supporting 'scm' versions older than 2.1.0 (tested with 2.0.2)

Version 0.1 (Nov 10 2011)

* Initial version


  1. Unknown User (tianlinzx)

    Any Release Plan? When will this plugin be available ?

    1. Unknown User (deluan)

      I've released a 0.1 version today, and it should appear in the update center in the next few hours.

  2. Unknown User (jacky)

    I also need this plugin, Why still do not appear?

    1. Unknown User (deluan)

      There seems to be a problem in the publishing mechanism for new plugins (other plugins are also being affected). I already reported it and am waiting for a solution and/or directions.

  3. Unknown User (cristian_beraha)

    Hi Deluan, did you tried to work with RTC through RTC/JAZZ API?

    1. Unknown User (deluan)

      Not really. Before developing this plugin, I tried to use an old Hudson plugin that uses the API. But it was developed for RTC 2.0 and I'm using 3.0. So I'd need to update it.

      Instead of trying to update the plugin, I decided develop a new one using the command line interface, because a plugin developed with the API cannot be distributed with the IBM's jars.

      1. Unknown User (cristian_beraha)

        I tried the same, and modified the code to fit RTC 3.0, makeit work only on master, of course I was forced to put all the dependencies for 3.0 (was painful), and was no good to work with API as it didn't performed well on slaves.

        The limitation of use only SCM  command line is that it is not possible to connect with build definitions and then finally reporting the results to RTC. I thought of developing some kind of RESTful service that can be distributed independently from IBM jars to provide more integration to RTC.

        1. Unknown User (deluan)

          I'm already developing the integration with the Jazz Team Build (and reporting build results back to RTC), using the Ant Build Toolkit. Soon will have a new version.

          I didn't test this on slaves (because I only have one Jenkins server here). Any help would be welcome... ;)

  4. Unknown User (jacky)

    Hi Deluan, I found an issue when i download latest code via this plugin, "ERROR: Timeout after 300 seconds", I tried to use command to do same things, no any issue. I did like to know how to solve it, would you like to help me ? By the way, RTC version is 2.0.2 , Jenkins version is 1.437 , Thanks 

    1. Unknown User (deluan)

      Please, create an issue on JIRA, attaching the full log from Jenkins. Thanks.

  5. Unknown User (bbonn)

    Hi Deluan,

    Thanks for writing this plugin.  Our company is transitioning to RTC and we are a big Jenkins shop.  I was experimenting with the plugin and can't seem to get it to pick up changes and kick off builds.  Looks like this should be working according to the wiki here.   I have it set Jenkins to poll every minute.  Anything I should look for?  Any other logging available?


  6. Unknown User (vbaskar)

    Hi Deluan,

    Thanks for the nice plugin. As an improvement can the password be masked when load command is printed in console output. After configuring the properties for this plugin, when a build is started it prints the RTC load command executed along with the user name and password in console output. Relieving the password is risky. Example snippet is copied below. It will be nice if the password is masked, some thing like *******. Do let know if additional info is needed

    Started by user DEMO_USER
     Building remotely on DEMO_BLD_SERVER
     $ /path/to/rtc/scmtool/scm load DEMO_STREAM -u DEMO_USER -P demo_user_password -r https://myrtcserver.com:9443/ccm -d /path/to/jenkins/build/workspace -f

    I have created an JIRA issue for this JENKINS-11863


  7. Unknown User (marcosmuniz)

    I  installed the RTC client on machine and I'm getting this error:

    $ lscm.bat compare ws "XXX Stream Workspace" stream "XXX Stream" -u ******* -P ******* -r https://rtc.xxx.com:6001 -I s -C "|

    Unknown macro: {name}


    Unknown macro: {email}

    |" -D "|yyyy-MM-dd-HH:mm:ss|"
    The java class is not found: com.ibm.team.filesystem.cli.minimal.client.FrontEndClient

    do you have any idea why this is happenning?


    1. Unknown User (deluan)

      Hi Marcos,

      Please raise a JIRA with more information (OS, SCM version, complete log as attachment, ...)



      1. Unknown User (marcosmuniz)

  8. Unknown User (schmagfran)

    Hey Deluan,

    First off, thanks for sharing this plugin.

    I was wondering if you could add the functionality to selectively load Components. We keep all of our components in a single workspace. We would like to create a Jenkins job for each component. The plugin in its current form loads the whole workspace for each job, wasting a huge amount of space, and a change in one component would trigger a build in all other components/jobs.

    Could you please extend the plugin so that it is possible to provide a single component to load? The command would look something like this:

    lscm load "worspaceName" "componentName" -u *** -P *** -r http://foo -d /absolute/path/toJenkinsWorkspace -f

    Again, keep up the good work.


    1. Unknown User (deluan)

  9. Unknown User (angusmccall)

    I added a bug as we are still getting an error each time there are new change sets to accept. It does work on initial checkout but the -s option seems to be wrong.

    Good work by the way! When is the next release?

  10. Unknown User (julian)

    Hi, when I try to checkout with this plugin, while the workspace has (unaccepted) pending changes I get some error.

    com.ibm.team.filesystem.cli.core, Version 2.0.2.I201107281653
    Unterbefehle: help version
    $ lscm.bat accept -u ***** -P ******* -d C:\CI\Jenkins-1.447.1\jobs\RTC-checkout\workspace -s MasterStream --flow-components -o -v -c 1019
    Fehler bei Ausf�hrung von 'accept':
    Beim Akzeptieren bestimmter Žnderungssets kann nur ein einziger Arbeitsbereich aktualisiert werden. F�hren Sie den Befehl mit der Angabe --target erneut aus, um anzugeben, welcher Arbeitsbereich aktualisiert werden soll.
    ERROR: Failed to run accept -u build -P build -d C:\CI\Jenkins-1.447.1\jobs\RTC-checkout\workspace -s MasterStream --flow-components -o -v -c 1019
    Finished: FAILURE

    The german part of the error message says something like: While performing 'accept': When accepting certain changeset, only one Workspace can get updated. Execute the command again (and specify --target) to indicate which work area is to be updated.

    Does anyone know if its my fault? And how to fix it?

    System: Windows 2008 R2, Java SE 1.7.0_03-b05, Java HotSpot 64-Bit  Server VM 22.1-b02, Jenkins 1.447-1, RTC Plugin Version 0.3

    EDIT: It still doesnt work with the plugin. But i found a workarround with cmd scripts, which fits for me.

    1. Deleting old Workspace

    2. lscm load --force build_space -u username -P password -r https://serveradress:9443/jazz/


    lscm compare ws build_space stream Master -u username -P password -r https://serveradress:9443/jazz/ -I s -C "|{name}|{email}|" -D "|yyyy-MM-dd-HH:mm:ss|"

    4. lscm accept -u username -P password -r https://serveradress:9443/jazz/ -s Master -t build_space --flow-components -o -v

    5. lscm deliver -t Stable -u username -P password

    1. Unknown User (jeremy lam)

      I have had success by creating workspaces that are only to be used by the Jenkins RTC plugin, and which are not to have items checked into them.

      On the Job configuration page under "Build Workspace", it states: 

      This is the workspace you have created for the builds to run from. Jazz best practice suggests this is a dedicated workspace.

  11. Unknown User (hwyin@cn.ibm.com)

    Hi,I hope to integrate this plugin to Hudson.But i cannot find the download path to download this plugin and how to integrate it to Hudson. Anyone who can help me? Thanks!

    1. Unknown User (deluan)

      You can download the plugin from this site: http://updates.jenkins-ci.org/download/plugins/rtc/ and install it manually on Hudson.

  12. Unknown User (sdetweil)

    It appears there is a problem with handling incomplete accepts..

    when the scm accept command is execute, the repository url is not specified..

    and when the error message is displayed, the username and password are shown in the clear.

  13. Unknown User (dbeerens)

    Hi Deluan,

    At one of my Jenkins (v1.5.00, Jenkins-Slave) build systems I get the following error message, when lscm accept commands needs to execute:

    FATAL: null
    at com.deluan.jenkins.plugins.rtc.commands.AcceptCommand.<init>(AcceptCommand.java:30)
    at com.deluan.jenkins.plugins.rtc.JazzClient.accept(JazzClient.java:126)
    at com.deluan.jenkins.plugins.rtc.JazzClient.accept(JazzClient.java:107)
    at com.deluan.jenkins.plugins.rtc.JazzSCM.checkout(JazzSCM.java:104)
    at hudson.model.AbstractProject.checkout(AbstractProject.java:1331)
    at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682)
    at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587)
    at hudson.model.Run.execute(Run.java:1557)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:236)


    When I run the lscm command myself from the CLI, all is okay, no java.lang.NullPointerException.
     I've noticed the command is run without the '-r' option (so I did as well, to mimic all the steps this jenkins-rtc integration is providing to resolve this error).
    What could be the problem?

    By-the-way: My other Jenkins Build System runs okay (v1.501, Stand-alone Jenkins (no, not the Master of the previously mentioned test Jenkins Build system)).

  14. Unknown User (yzaltz)

    Have the same Error - v. 1.505. 
    anyone have a root cause?

    1. Unknown User (roystons)

      That particular variant of that error is caused by the version number not being detected correctly for newer (v4+) versions of RTC.  There are various patches - some already applied, some as pull requests - that will fix this.  I'm hoping to get them applied properly and a real build soon.

      Best to raise issues in the issue management system rather than here, however.

  15. Unknown User (shonuff)

    Hi Deluan,

    Using this plugin, are the properties defined in the RTC Build Definition available to Ant as launched by Jenkins? If so, how do I reference them?

    (I've already tried property.name and env.property.name.)