[JIRA] Updated: (HUDSON-7104) Clearcase Plug-in 1.3 polling broken

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[JIRA] Updated: (HUDSON-7104) Clearcase Plug-in 1.3 polling broken

Kohsuke Kawaguchi

     [ http://issues.hudson-ci.org/browse/HUDSON-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

raspy updated HUDSON-7104:


> List<ClearCaseChangeLogEntry> entries = action.getChanges(new Date(), "IGNORED", new String[]{"Release_2_1_int"}, new String[]{"vobs/projects/Server"});
> Is is a viewpath that is unrelated to what is defined in cleartool command.

It is unimportant what is the last path, since lshistory is not actually called in the testcase. Call to lshistory will be replaced by Expectations object, which will return value as specified (regardless of arguments - see all those with(any(...))). What this test does is checking that viewpath is removed from lshistory output (so that "/view/ralef_0.2_nightly/vobs/Tools/framework/util/QT.h" is converted to "/vobs/Tools/framework/util/QT.h").

> Also I can see that getChanges() is used in test code only but not in prod. code. Is this method replaced?

No, it isn't. It is called in AbstractClearCaseScm.saveChangeLog() which in turn is called in AbstractClearCaseScm.checkout().

> Clearcase Plug-in 1.3 polling broken
> ------------------------------------
>                 Key: HUDSON-7104
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-7104
>             Project: Hudson
>          Issue Type: Bug
>          Components: clearcase
>    Affects Versions: current
>         Environment: RedHat Linux
>            Reporter: javakrieg
>            Assignee: vlatombe
>         Attachments: build.xml
> I was using Hudson 1.366.  After I installed the new Clearcase 1.3 plug-in, I noticed that polling no longer detected changes in my Clearcase vobs.  Polling would generate a normal report, but report no issues found.
> I just updated to Hudson 1.368 and the same thing is still happening.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira