-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Linux x64, Hudson 1.393, Clearcase plugin 1.3.5
When ClearCase configuration is changed, polling should be done since last build time. Currently it is only done since last polling and may miss changes as follows:
1. Config asks to check for changes in /vobs/vobA, /vobs/vobB.
2. A build is done.
3. Developer changes files in /vobs/vobsC.
4. Polling runs for /vobs/vobA and /vobs/vobB.
5. Config is updated to include /vobs/vobsC in load rules.
6. Polling runs for /vobs/vobA, /vobs/vobB and /vobs/vobC, but since it runs since (4), it misses the changes from (3).
I suggest that after every Clearcase configuration change revert to polling since last build instead of since last polling.
Load rules are recorded in SCMRevisionState for each polling. So if you changed the configuration to include a new load rule, the polling logic should be able to detect that and trigger a new build.