Sorry, apparently Google is REALLY slow at indexing groups, so I haven't
yet received a notification for this post.
This is a problem with core, like many others have described. The main
build will always sync first, and there's really no way (that I know of) to
get around it.
I suggest you change your client spec name to "Jenkins_${JOB_NAME}" and
turn off force syncing to make things move a bit faster.
On Thursday, 1 March 2012 04:34:21 UTC-7, Thomas Fields 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.
>
