Dup JENKINS-6999 and fixed in 1.3.1

I updated to Clearcase plug-in 1.3.1 and the problem remains.

2 file changes should have been detected here:

Started on Aug 6, 2010 2:46:05 PM
[hudson_gem_developer_view] $ /usr/atria/bin/cleartool pwv -root
/view/hudson_gem_developer_view
[workspace] $ /usr/atria/bin/cleartool lsview hudson_gem_developer_view

• hudson_gem_developer_view /b/uviews/agitarmr/hudson_gem_developer_view.vws
  [workspace] $ /usr/atria/bin/cleartool startview hudson_gem_developer_view
  [hudson_gem_developer_view] $ /usr/atria/bin/cleartool lshistory -all -since 6-aug-10.19:31:10utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \n%c\n' -branch brtype:hudson_gem_developer_view -nco vobs/mxutil
  Done. Took 12 sec
  No changes

Without more input, I cannot help, the cleartool lshistory shows no change on the branch (hudson_gem_developer_view) and load rule you indicate (vobs/mxutil). It there anything I'm missing?

Something is wrong with the timestamps used to do the search.

Log states:
Started on Aug 6, 2010 4:01:05 PM
[hudson_gem_developer_view] $ /usr/atria/bin/cleartool pwv -root
/view/hudson_gem_developer_view
[workspace] $ /usr/atria/bin/cleartool lsview hudson_gem_developer_view

• hudson_gem_developer_view /b/uviews/agitarmr/hudson_gem_developer_view.vws
  [workspace] $ /usr/atria/bin/cleartool startview hudson_gem_developer_view
  [hudson_gem_developer_view] $ /usr/atria/bin/cleartool lshistory -all -since 6-aug-10.20:47:08utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \n%c\n' -branch brtype:hudson_gem_developer_view -nco vobs/mxutil
  Done. Took 5.8 sec
  No changes

My local time is 4:01 PM (CST). The last build took place today at 10:47 AM (CST). It is searching for changes in the future (20:47:08utc+0000) and not finding any.

Notice also that the time stamp it is using to search with has changed since the last log I posted. It continues to search in the future with a changing date, instead of using the date of the last successful build.

• Polling is done using GMT time (+0000). CST is GMT-6 so it seems normal that it adds 6 hours to your time.
• Also, since 1.3, the polling time is recorded, so the polling is done since the last polling instead of the last build (only the first polling will poll with last build time)

When does the plug-in decide to poll with the last build time vs. the last build time? After reboot? After a new build?

Are the Clearcase pollings logged in a persistent file, or does each poll replace the last? It would good to see a history of the polling output to help debug the issue.

I can try some experiments to further pinpoint why the polling is failing.

I think it is risky to store the polling time vs. using the last successful build time. If something fails (like I am experiencing) the polling will never work again for those changes.