Is Continuous Integration possible with ClearCase?

If you are using UCM, you can also consider the ClearCase UCM Plugin, and only trigger a build on demand, when a baseline is created.

That way:

• the developer controls when a continuous build is appropriate, but adding a baseline (and cleaning old ones if needed).
• Jenkins can promote baselines, making it easier to trace what build has succeeded or failed.

You can even provide a script for the developer to use for:

• check-in all the current checked-out file
• set a baseline automatically

That would help the user trigger that continuous integration, since he/she can decide when the current code base is stable enough to be committed (and tested).

You can still use that idea with base ClearCase: simply make sure to put a shifting label on all the file (shifting means: if a file has a previous version with that label, the label would be moved to the LATEST version just checked-in by the developer).

Your Jenkins CC view would be configured to display all files with that label, which means if said label moves to a new version, the cleartool lshistory done by Jenkins will change, and a build will be triggered. (Note: you cannot yet do it for a pattern of label)

There is a clearcase plugin https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+Plugin It looks a bit complex to implement but has recent updates.

On the other hand, you could bridge to git/svn How to bridge git to ClearCase?