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 ch
On Mon, Mar 5, 2012 at 9:26 AM, Thomas Fields wrote:
> I'm not sure about the SVN plugin but it's a performance killer for me
> so I'm hoping there is a fix. I've created
> https://issues.jenkins-ci.org/browse/JENKINS-12983 to see if I can get an
> official answer from the author of the Perforce p
I'm not sure about the SVN plugin but it's a performance killer for me
so I'm hoping there is a fix. I've created
https://issues.jenkins-ci.org/browse/JENKINS-12983 to see if I can get an
official answer from the author of the Perforce plugin.
On Saturday, 3 March 2012 15:58:16 UTC, Simon St
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 wrote:
> Hi there,
>
> I've been using the Perforce plugin with Jenkins for a while now and it's
> been working great. However, recently
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 "p
