The solution to this is to increase build-pipeline refresh to large value,
i set it to 30 seconds. I have not see this happen again
On Friday, July 18, 2014 4:53:02 PM UTC-7, abhinavn wrote:
>
> Hi
>
> I have lot of integration tests and as the tests keep running if another
> job
This is not related to jenkins, for cloning large git repo you need to
follow shallow clone
http://blogs.atlassian.com/2014/05/handle-big-repositories-git/
On Friday, July 18, 2014 11:50:52 PM UTC-7, bandi pavankumar reddy wrote:
>
> Hi friends i am trying to clone 18 GB repository in Jenkins it
I ran ino the exact same problem today, but we are not using name-setter
plugin in our project
On Friday, April 25, 2014 1:11:26 PM UTC-7, Dilip M wrote:
>
> Are you using a build-name-setter plugin in this job?
>
> For us, we were using it. Having stopped that, we are not seeing this
> problem.
