Developed by

Sponsored by

Config Rotator, now with Git support


In ClearCase UCM a composite baseline describes dependencies between different baselines of components in a parent/child relation.

This 'dependency graph' in a composite baseline describes a configuration, where one specific baselines defines a relation to other specific baselines – potentially nested in several layers.

But it can also be regarded as a more generic structure that simply describes a hierarchy of components.

When viewed as a hierarchy it's interesting to know, if another (newer) component in the structure would still be compliant with the configuration as a whole. Somebody ought to test
that each time a new baseline of a component in the hierarchy is released.

The Config Rotator monitors the SCM for newer versions of components in the structure, and executes this test when necessary. The configuration is only created temporary and only the
result of the try-out is stored. The actual tested configuration is not persisted. Component developers can subscribe to test results involving their components through ATOM feeds on the Jenkins job running the Config Rotator.

Supported SCMs

Feature highlights

Requirements and recommended setup

ClearCase UCM

  1. You need a working ClearCase environment for the user running the Jenkins build on the host (Jenkins master or slave) where the build is executed
  2. Plugin is in current version only tested on Windows
  3. Freestyle builds must be used
  4. Jenkins slaves are tested running as a service, or Java Webstart (it's important user running service or Java has a working ClearCase environment)

Future plans might be Linux support or other ways to setup job and master/slave. If you are using the plugin in other setups than the above, kindly let us know if it works or not.


Git requires no special setup.

Getting Started Guide

In the Source Code Management section select the Config rotator option

ClearCase UCM Configuration

The Context Project VOB is where the UCM project of the temporary stream is located. In this Project VOB a special UCM Project must be created and named jenkins
Contribute data globally will write the resulting action of a config rotator build to a database specified in global configuration under the global configuration page:

The UCM configuration is a series of baselines describing the configurations.


Feature description

Trying a series of configurations

Picture show a series of successfull build. The project/job page will show latest result for the configuration. If You click on the a build the tested configuration from the build is shown.

Click the Config Rotator link in the left menu on the project/job to view all tried configurations

Using feeds

Reset to old configuration

If You wan't to try a configuration once more, and continue from that time on, go to the job, click a build and on the build page click Reset to this configuration

Changes link working on component baselines

We have implement the Changes feature to show changes between the baselines of the changes component in the configuration.

Known Issues (current version)

If it's broken ...We Can Fix It!


Version 2.0.0(August 25, 2016)

Version 1.3.1(October 12, 2015)

Version 1.3.0(August 28, 2015)

Version 1.2.1(August 18, 2015)

Version 1.2.0(July 6, 2015)

Version 1.1.8(Januar 29, 2015)

Version 1.1.8(November 17, 2014)

Version 1.1.7(August 16, 2014)

Version 1.1.6(June 23, 2014)

Version 1.1.5(May 2, 2014)

Version 1.1.4(March  11, 2014)

Version 1.1.3(December 20, 2013)

Version 1.1.2(August 26, 2013)

Version 1.1.1(June 4, 2013)

Version 1.1.0(April 14, 2013)

Version 1.0.4(April 3, 2013)

Version 1.0.3(April 2, 2013), faulty release

Version 1.0.2

Version 1.0.1

Release note

We have implemented two levels of check of configuration. The first check is if configuration is loadable in ClearCase. The second level of check is if the configuration added make sense in a context of configuration rotation. Eg. config-rotator does not allow the same component more the once.

Polling check the first level, and abort polling if check is not passed.
Builds do both checks and fail if not passed.

Version 1.0.0, initial version