Change Log
by Ben Acord · 11/30/2007 (9:05 pm) · 7 comments
As a follow up to my last .plan, I'm about to release to the community my script that reports on all modified files within a day range. Here's the screenie:
There is still some code to clean up and I need to finish the stylesheet but it is a real time saver. The report can be scheduled and dump the daily change_log.html file into your documentation directory prior to daily backups. That way the days activity is saved with each backup set.
The missing flag field will either be dropped or have an icon indicating the violation caught. The violation of "TGE" is a test case but will be replaced by the default word "vanilla" to alert any modifications to the vanilla directories.
It's very fast; parsed all 27,210 files in my c:\Torque directory in about 5.5 seconds.
Here's the current help syntax:
More on the way in the next few days. If you have any suggestions or feedback based on this help syntax and a screenie feel free to comment accordingly.
There is still some code to clean up and I need to finish the stylesheet but it is a real time saver. The report can be scheduled and dump the daily change_log.html file into your documentation directory prior to daily backups. That way the days activity is saved with each backup set.
The missing flag field will either be dropped or have an icon indicating the violation caught. The violation of "TGE" is a test case but will be replaced by the default word "vanilla" to alert any modifications to the vanilla directories.
It's very fast; parsed all 27,210 files in my c:\Torque directory in about 5.5 seconds.
Here's the current help syntax:
Usage: Modified_Report.pl [ --help ]
Optional Arguments:
[ --searchdir=<subdir_name> ]
[ --days=<number> ] | [ --startdate=<mmddyyyy> | [ --enddate=<mmddyyyy> ] ]
--help Show this usage text. Also shown for --h and --?.
--searchdir Constrain the search to a specific subdirectory;
just the subdirectory name not a full path.
--days=<number_of_days> Expand the search to include days before the past 24-hours.
Default=1.
--startdate=<mmddyyyy> Set a search start range. Must be in the form mmddyyyy.
--enddate=<mmddyyyy> Optional: Set a search end range. Defaults to today.More on the way in the next few days. If you have any suggestions or feedback based on this help syntax and a screenie feel free to comment accordingly.
About the author
#2
I also intend on including shell scripts that call the common options (1 week of changes, image/code/model only, etc.).
edit: removed tags.
12/01/2007 (12:49 am)
Sounds like a plan. I'll update the backup script with a new --i option to indicate an incremental backup. I also intend on including shell scripts that call the common options (1 week of changes, image/code/model only, etc.).
edit: removed tags.
#4
12/01/2007 (5:38 pm)
You should sell this its great!
#5
So with that said, does anybody want to test and certify ChangeLogger.pl and the Backup_Game.pl Perl scripts for Mac, Linux, and Vista too?
If it's received well enough maybe I should look into making them resources. Though honestly I don't know what all that entails.
First the good news; last night I enhanced the header to include your company/game logo in the top right and added statistics for the total number of files included in the search (now with commas for readability). I've updated the screenie in the post to show the changes. The logo has a lot of whitespace above and below and is flushed top-right.
Now for the bad news; while profiling the script I found that it wasn't fully recursing all subdirectories but was hanging out too long in others. Eek. Once fixed, the run time jumped up from 5 seconds to 11.5 and at times 15 seconds depending upon search criteria. Of course, this is still better than the 3 minutes and 10 seconds it takes for the Windows search tool...and it doesn't give a usable report as output.
12/01/2007 (6:32 pm)
Thanks Neill. This type stuff is so foundational to any game house that I'm going to keep them free (GPL). Both scripts still need to be tested for Mac and Linux because I really want them to be 100% platform independent. There are still some Windows centric stuff to be reworked.So with that said, does anybody want to test and certify ChangeLogger.pl and the Backup_Game.pl Perl scripts for Mac, Linux, and Vista too?
If it's received well enough maybe I should look into making them resources. Though honestly I don't know what all that entails.
First the good news; last night I enhanced the header to include your company/game logo in the top right and added statistics for the total number of files included in the search (now with commas for readability). I've updated the screenie in the post to show the changes. The logo has a lot of whitespace above and below and is flushed top-right.
Now for the bad news; while profiling the script I found that it wasn't fully recursing all subdirectories but was hanging out too long in others. Eek. Once fixed, the run time jumped up from 5 seconds to 11.5 and at times 15 seconds depending upon search criteria. Of course, this is still better than the 3 minutes and 10 seconds it takes for the Windows search tool...and it doesn't give a usable report as output.
#6
12/01/2007 (6:44 pm)
15-20 seconds isn't that long really. I'd be happy to test the Vista version. Looks like this would be a great resource.
#7
12/01/2007 (10:23 pm)
It's now tuned to the following (Search criteria was changed files within two days):11.000 seconds 27,220 files (that's everything). 4.800 seconds 11,450 files (Art subdir only). 2.432 seconds 5,743 files (stock TGE 1.5.2 only). 0.573 seconds 1,297 files (business docs only). 0.203 seconds 450 files (modernization kit only). 0.046 seconds 75 files (Documentation subdir only).
Torque Owner Johnathon