git "checking for modifications" checks on first build on large repository (Bug #219)

Added by Harald Deischinger over 5 years ago. Updated about 4 years ago.

Status:Closed Start date:10/23/2012
Priority:Low Due date:
Assignee:- % Done:


Category:- Spent time: -
Target version:1.8.5
Affected version:1.8.2


Checking for modifications fails with a timeout on repositories with long history as it tries to pull a full log.
(from the docu: "If the project has not yet been integrated, a "git log origin/$BranchName --name-status -c").
For a project with >10 years of history pulling such a log can be quite time consuming.

So when using on an existing repository with long one has to add a dummy "last-commit" entry.

I would suggest to get no history when doing an initial build.


Updated by Koen Heye over 5 years ago

I'm currently experiencing the same problem! Can you explain how you worked around it by using the "last-commit" entry? Which git command did you use?

Updated by Harald Deischinger over 5 years ago

I modified the ".state" file.
Adding the SourceControl line helped (I have copied some more lines to show the context):

<FailureUsers />
<FailureTasks />
<SourceControl name="commit" value="11213fcfd6e902a2b0be696b94d936e0b32d67b0" />

As commit-value I used the commit hash of the last successful build of the old builder, but actually you can use any recent commit-hash.


Updated by Ruben Willems over 5 years ago

  • Target version set to 1.8.4

Updated by Ruben Willems almost 5 years ago

this should be rather easy since the integration result has a property 'isInitial'

Updated by Ruben Willems almost 5 years ago

  • Target version changed from 1.8.4 to 1.8.5

Updated by Ruben Willems about 4 years ago

feature has been added : MaxAmountOfModificationsToFetch
default value is 100
so it fetches only the last 100 modifications

  • Status changed from New to Closed

Also available in: Atom PDF