Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
| |||||
This is a request from our IT Audit group. For each project, please create a report of project source changes during the period of 6/15/2011 through the present.... I used the following commands: si report --basename=xxx --project=d:/MKSprojects/project.pj si rlog --project=d:/MKSprojects/project.pj --rfilter=daterange:'"June 15, 2011 - 6:07:28 AM"'-'"June 25, 2012 - 6:07:28 PM"' si diff -r 1.3 -r 1.16 --project=d:/MKSprojects/project.pj > test.xls si mods -r 1.1 --project=d:/MKSprojects/project.pj I had no luck...contacted MKS support. They are working on a solution too.... Please note for "si report" I got 6 files in my cygwin home directory - .txr has revision information but shows changes from r1.1 to r 1.5, but our latest version is 1.16......also this is not considering the dev variants I tried output redirection (>) to various file formats, however, there is a need for some formatting from within MKS commands itself. The reason being the resulting excel file will not be in a table format….I’m researching the “--fields” command (not with much success). If I’m not mistaken in MKS integrity 2005, the “si report” command would output data into MS Access (fully formatted)….don’t know why MKS scrapped that function.. I've used the Perforce "p4v logger" to create weekly audit reports. Can anyone help please? |
| |||
Posted By: mlizak Posts: 72 / Registered: Feb, 2011 | |||
Hello Suman, Please also ask your Support Engineer to add you to the RFC for Source Reporting. I suspect a combination of the commands you have listed with some massaging from Perl or some other scripting language might be useful, but I don't have any scripts that come close to doing that myself. Regards, Kael |
|