Since upgrading from Clearcase plugin version 1.2.1 to the latest release (1.3), the plugin has stopped detecting SCM changes. I am using Base Clearcase with snapshot views. The Clearcase plugin is set to poll for changes every 5 minutes.
When the build is triggered manually, the correct change history is generated, but polling never detects any changes. The Base ClearCase Polling Log shows that lsview has been run (successfully) to confirm that the view exists, but there is no sign of lshistory being called to check for updates. This was working correctly with the same job configuration using the previous release version of the plugin.
Sample polling log (with HUDSON_CLEARCASE_VERBOSE environment variable set to '1'):
It seems that AbstractHistoryAction.runLsHistory is exiting after calling lsview but before calling lshistory. Since the lsview check is successful, the only way that could happen seems to be if the viewPaths string array parameter is empty.
A recent change to AbstractClearCaseScm.compareRemoteRevisionWith() would seem to be the culprit.
Looking at the revision history, it seems that this was changed recently to get the loadrules from the AbstractClearCaseSCMRevisionState passed to the compareRemoteRevisionWith() method (the call to ccBaseline.getLoadRules(). Earlier versions called AbstractClearCaseScm.getViewPaths(). However, I've looked at where the ClearCaseSCMRevisionState is created (ClearCaseSCM lines 399-407), and nothing seems to call setLoadRules() to actually set the load rules in the revision state.
Of course, I might be barking up the wrong tree with diagnosis - I only started looking at the source code today!