Max limit for commits and tag observation

[Former user]

Hello, first I want to thank you for this PlugIn. In second, I have the following questions: What is the max limit for commits? Currently I am having a project with about 38000 commits, but in the Jigit config section it just says 2594.

Can I also observe tags?

Thank you in advance, Marcel

[Dmitrii Apanasevich]

Hi!

What is the max limit for commits? Currently I am having a project with about 38000 commits, but in the Jigit config section it just says 2594.

This looks like a problem. There are no limits in number of fetched commits. Did you look at JIRA log? Maybe you'll find some errors there. The problem can be due to a huge commit with lots of changes. Such commits are very heavy and can lead to connection timeout errors during commit fetching. Jigit has parameter in repo configuration Commit Request Timeout for this case. Look for such errors in log and if you'll find them try to increase this parameter up to 30 seconds for example.

If you want me to help you in research of the log, you can attach your JIRA log to a comment.

Can I also observe tags?

No, it's not possible now. How do you think it should be implemented? Where you want to see tags?

[Marcel Höll]

The following error is printed out in the log file of Jira:

2017-09-06 09:53:16,871 Caesium-1-1 ERROR ServiceRunner     [jigit.indexer.JigitIndexer] JigitIndexer::execute - ExecutionException. Cause: 
java.lang.IllegalArgumentException: Cannot set non-null String field TITLE to ''
    at com.google.common.base.Preconditions.checkArgument(Preconditions.java:145)
    at net.java.ao.EntityManager.create(EntityManager.java:347)
    at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.create(EntityManagedActiveObjects.java:86)
    at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects.create(TenantAwareActiveObjects.java:261)
    at sun.reflect.GeneratedMethodAccessor1780.invoke(Unknown Source)
    ... 1 filtered
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
    at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
    at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
    at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
    at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
    at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
    at com.sun.proxy.$Proxy1849.create(Unknown Source)
    at jigit.ao.CommitManagerImpl.create(CommitManagerImpl.java:61)
    at jigit.ao.CommitManagerImpl.persist(CommitManagerImpl.java:148)

This is the only error which is printed out, but many times...

[Marcel Höll]

To observer the tags, isn't it nearly the same as observing "normal" commits, just in another folder? See https://stackoverflow.com/questions/27149949/list-commits-associated-with-a-given-tag-with-jgit

[Dmitrii Apanasevich]

This is the only error which is printed out, but many times...

Well, it's a bug. I'll give you more information later, I have to research it first. Only one question now: which DBMS do you use? Oracle?

[Marcel Höll]

The underlying database of JIRA is a MySQL DBMS and we are using GitLab in our own environment. I don't know now, which DBMS GitLab is using...

[Dmitrii Apanasevich]

There is a commit with empty message in your repo which causes this issue.

I've reproduced and fixed the bug. Also, I've written a test for such case. New version 1.0.3 has already available in Marketplace. Please, download and install it.

Please, inform me whether everything is ok with indexing of your repo in new version of add-on.

[Dmitrii Apanasevich]

My bad: it was a wrong class import. I've uploaded version 1.0.4 to the Marketplace. This time I've checked it better.

Foolish mistake, sorry for inconvinience.

[Marcel Höll]

Thank you very much, maybe somtime are you be willing to implement the same for tags? I think it will not be the biggest problem. I've tested the public API of Gitlab and it is working great!

[Dmitrii Apanasevich]

Can I close this bug? Have your 38K commits already indexed?

maybe somtime are you be willing to implement the same for tags?

Please, create a new issue for the feature about tags. I should take a look on API and think about this feature in general.

[Marcel Höll]

Yes thank you, now all 36193 commits have been indexed.