-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
when lshistory is run the filepaths returned are relative to where the command
is run from. Currently we run lshistory from the viewroot.
This results in the loadrule(s) being prefixed each changed file e.g. if the
load rule is vobs/MyClient/MyProject all files will look like
/vobs/Myclient/MyProject/MyComponent/src/main/java/etc...
Suggest we provide a option to run lshistory inside each loadrule so to avoid
long prefixes. In the above case the files would then look like
MyComponent/src/main/java/etc..
Related to this is that the current clearcase plugin (0.6) grabs the changeset
for the entire view, regardless of load options because lshistory is ran in the
view root.
For example, the particular view may contain packages A, B and C. A Hudson job
is configured with a config spec to load A/ and and another Hudson job is
configured to load B/ but when the CC plugin calls lshistory, it will grab the
changeset for the entire view: A, B and C. This distorts the change set
history/SCM change polling and the email notifications that only mail to
contributors.
In essence, the CC plugin should be enhanced to run lshistory so that it only
shows the change sets for the configured loaded directories.