There's a minor issue in the Perforce modification reporting. The following is a (slightly censored) extract from our build log.
2009-01-30 11:47:10,276 [Tools:DEBUG] Starting process [p4] in working directory [] with arguments [-s -c CodeBuild -p perforce:1666 -u Read.Only -P NoWriting changes -s submitted "//depot/Source Code/ Independent..."@2009/01/30:11:08:43,@2009/01/30:11:47:10 "//depot/ Source Code/PC..."@2009/01/30:11:08:43,@2009/01/30:11:47:10 "//depot/ Source Code/Middleware/..."@2009/01/30:11:08:43,@2009/01/30:11:47:10 "//depot/Source Code/Project/ Tools/..."@2009/01/30:11:08:43,@2009/01/30:11:47:10 "//depot/Source Code/Project/Axon/..."@2009/01/30:11:08:43,@2009/01/30:11:47:10 ] 2009-01-30 11:47:10,495 [1496:DEBUG] [Tools p4] info: Change 162015 on 2009/01/30 by *...@*** 'refactored' 2009-01-30 11:47:10,495 [1496:DEBUG] [Tools p4] info: Change 162015 on 2009/01/30 by *...@*** 'refactored' 2009-01-30 11:47:10,495 [1496:DEBUG] [Tools p4] info: Change 162015 on 2009/01/30 by *...@*** 'refactored' 2009-01-30 11:47:10,495 [1496:DEBUG] [Tools p4] exit: 0 2009-01-30 11:47:10,495 [Tools:DEBUG] Perforce plugin - running:FileName: [p4] -- Arguments: [-s -c CodeBuild -p perforce:1666 -u Read.Only -P NoWriting describe -s 162015 162015 162015] As you can see we have a view consisting of several subdirectories of the source root. If someone checks in a changelist spanning several of those, that changelist is returned for each one. This means we end up with duplicate entries. Would it be possible to change the p4 describe call to eliminate duplicates? -- Kim Randell Rebellion Developments
