I think there may be a bug with the matrix builds... I have noticed with SVN the parent does an unnecessary sync as well.
On 1 March 2012 21:34, Thomas Fields <thomasmfie...@gmail.com> wrote: > Hi there, > > I've been using the Perforce plugin with Jenkins for a while now and it's > been working great. However, recently I noticed that it's been doing what I > think is a redundant sync. > > I've got a matrix job and when the job triggers, the matrix parent gets a > list of the changes by calling "p4 describe" but I don't see why it > actually needs to sync the entire view. > > Here's a snippet of my console output for the matrix parent job: > > [LevelEditor] $ "C:\\Program Files\\Perforce\\p4.exe" counter change > [LevelEditor] $ "C:\\Program Files\\Perforce\\p4.exe" -s changes -s submitted > //Jenkins_LevelEditor-Build1/...@167107,@167107 > [LevelEditor] $ "C:\\Program Files\\Perforce\\p4.exe" describe -s 167107 > [LevelEditor] $ "C:\\Program Files\\Perforce\\p4.exe" -G where //... > Sync'ing workspace to changelist 167107 (forcing sync of unchanged files). > > [LevelEditor] $ "C:\\Program Files\\Perforce\\p4.exe" -s sync -f > //Jenkins_LevelEditor-Build1/...@167107 > > > Then each sub-element of the matrix does this: > > [x86] $ "C:\\Program Files\\Perforce\\p4.exe" counter change > This is a matrix run, trying to use change number from parent/siblings... > Latest change from parent is: 167107 > [x86] $ "C:\\Program Files\\Perforce\\p4.exe" -s changes -s submitted > //Jenkins_LevelEditor-CONFIG-Debug-TARGET-x86-Build2/...@167107,@167107 > [x86] $ "C:\\Program Files\\Perforce\\p4.exe" describe -s 167107 > [x86] $ "C:\\Program Files\\Perforce\\p4.exe" -G where //... > Sync'ing workspace to changelist 167107 (forcing sync of unchanged files). > [x86] $ "C:\\Program Files\\Perforce\\p4.exe" -s sync -f > //Jenkins_LevelEditor-CONFIG-Debug-TARGET-x86-Build2/...@167107 > > Note the same sync happens again. > > Is this a bug in the Perforce plugin? Is there anyway to remove that first > sync? As you can imagine, if your view is quite large, the sync could take a > while and slow down the build. > > Regards, > Tom. >
