# the files to generate the data for. any Perforce path works DepotPath=//guest/... # specify the target visualizer. currently code_swarm and gource are supported Visualizer=gource # ignore files with the specified extension when generating the data # use multiple lines to specify multiple values IgnoreExtension=.map IgnoreExtension=.derp # specify a starting changelist instead of starting at the beginning of time StartingChange=1 # this makes changes on branched versions look like they were done on the original file # helps to cut down on excessive noise from frequent dev branches Condense=true # verbose output Verbose=true # calculates the amount of the file that was changed per change. this affects the brightness of points in code_swarm but has no effect in gource CalculateWeights=true # shows job activity as file changes. only works with gource IncludeJobs=false JobModifiedDateField=ModifiedDate JobModifiedByField=ModifiedBy JobNameField=Job SpecDepotName=spec
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 8399 | Matt Attaway |
Add support for Gource friendly output With this change adding 'Visualizer=gource' to the config file will shockingly enough enable output for the quite excellent gource version control visualizer. To get a copy of gource visit: http://code.google.com/p/gource/ |
||
#1 | 8372 | Matt Attaway |
Add tool to generate data for the code_swarm version control visualizer. This tool generates the necessary data for code_swarm to display the evolution of your source code. It's unique in that it has options for compressing variants into one node, excluding paths and file extensions, and including jobs that are filed and fixed so that your QA people aren't left out of the fun. All details are in the ruby script. More info on code_swarm can be found at http://www.michaelogawa.com/code_swarm/ Thanks to @sam_stafford for the variant folding code. |