QC work/mktriggers progress/sync from Tandem issues
- Detailed which fields are currently getting QC Synchronized
- Updated vbs scripts to be more Unix like, accepting parameters, etc. and to be able to update the status both backwards and forwards, as well as have a -noexec mode.
- Met with ??? regarding QC synchronization
- Worked a lot with Randy on Evil Twin issues for Polaris
- Documented duplicate code problems
- Documented how to use dynamic views in Eclipse
- Working on trying to compare files from the pathway for SDDLS
- Worked on getting mktriggers.pl finished.
Issues with getsysid.pl
There is a script called getsysid.pl which will get stuff from the Tandem and ftp it locally. The hope was that we could just get stuff back from the Tandem and then use something like diff -r to compare things. There are some issue with that:
- Since files are coming off the Tandem their extensions are lost. Therefore while it may be foo.c when in Clearcase, it's just foo when it gets to the Tandem and thus when it comes back from the Tandem it's also just foo. diff -r will not be matching up foo and foo.c
- Typically views on Windows in transparent mode retain their CRLF characteristics. In other words they are in "DOS" mode. Files come back from the Tandem however are in "Unix" mode. This makes every line report as different from diff!
- There's the issue of these "squiggle" lines where version information is encoded in Clearcase and filled in on the Tandem (or visa versa). This lines, of course, will compare differently. Ugh!
Perhaps a tool that can take these differences into account...