[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:


vob path has initial / stripped by design. You see, vobs are not always available at root directory, you are probably tempted to think about vobs through the dynamic view which is set. However, the same vob could be available as /vobs/product in set dynamic view, as /view/some_view/vobs/product in dynamic view which is not set or as /usr/raspy/snapshots/snapshot_view/vobs/product in some snapshot view. Therefore what the plugin does is entering view path and then running lshistory for relative path (without /) vobs/product. Depending on configuration (dynamic/snapshot view and path) the working directory will be different, but the lshistory call can be the same.

See the console log that after 'cleartool startview' command, the current directory is no longer [workspace] when running lshistory.

I could make use of your trace plugin if you wish, but if its purpose is to check why / is stripped, I tell you now: it's by design :-)

Best regards,

> 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