Jigit Plugin is not Indexing Repositories other than Default
Hi,
We are using Jigit Plugin with Gitlab so we can see Git Check ins under our JIRA Tickets. GIT Plugin is only indexing the default Branch i.e. develop and not indexing other branches. First, I tried to mark check on "Index All Branches" but it only indexed the default branch. Then, I tried to manually add the other branches but it only showed "0" in front of other branches.
Could you please let me know if I am doing something wrong or there is any limitation with this plugin?
Appreciate your quick help in this regards.
Thanks Abid Raza
Comments (21)
-
repo owner -
repo owner Any news?
-
repo owner - changed status to wontfix
-
reporter Hi,
Please find the attached snapshots which shows the differences in the check in count in a repository.
-
reporter - changed status to open
-
reporter Hi,
There is no debug logging level under "Logging and Profiling". Please suggest.
Thanks Abid
-
repo owner Is the difference between numbers of commits the only issue? If so, it's not a promlem at all. It is mentioned here that the add-on indexes the default branch first. Therefore, already merged (or cherry-picked) commits won't be indexed and counted twice, as it is at GitLab side.
Do you have any commit to a branch which is not merged to the default branch and not displayed at Jigit tab?
-
reporter Hi,
Could you please let me know what should be the settings for Timeout, Sleep and Each Request / Seconds for checkins more than 35000.
I set them as:
Commit Request Timeout = 1000 sec Sleep = 5 sec each = 1000 requests
Furthermore, whenever there are new commits, they never appears in the Jigit Tab until we reindex the repository.
Also, Is there any way, I can attach snapshots here as I don't find anyway to show you what's happening here.
Thanks Abid
-
reporter Hi,
We have different branches going on in our release and we want their commits to show up in Jigit tab before merge. Is there any way, we can achieve this instead of giving all the branches which we need? Can it automatically fetch commits from all branches.
Thanks Abid
-
repo owner Could you please let me know what should be the settings for Timeout, Sleep and Each Request
Just leave default values. All cases which require tuning of these settings are described here
- Is there any way, I can attach snapshots here as I don't find anyway to show you what's happening here.*
In the right upper corner of this issue click More > Attach files
Is there any way, we can achieve this instead of giving all the branches which we need? Can it automatically fetch commits from all branches.
Yes, it is. It is also described in the link I've gave above. Just select "Index all branches" option in thre repo settings.
-
reporter I have already mentioned "Index All branches" but still I have to reindex after few days to get all checkins available in Jigit Tab. Please note: I sometimes see following error in JIRA logs. Could you please view the logs and suggest if there is any resolution for this error:
2018-12-24 09:37:47,651 Caesium-1-3 ERROR ServiceRunner [jigit.indexer.JigitIndexer] JigitIndexer::execute - ExecutionException. Cause: api.APIException: GitLab is not responding at api.client.http.ApiHttpRequester.handleError(ApiHttpRequester.java:130) at api.client.http.ApiHttpRequester.parse(ApiHttpRequester.java:109) at api.client.http.ApiHttpRequester.withResultOf(ApiHttpRequester.java:76) at api.client.http.ApiHttpRequester.withResultOf(ApiHttpRequester.java:63) at jigit.client.gitlab.GitLabRepositoryAPI.getCommit(GitLabRepositoryAPI.java:45) at jigit.indexer.api.gitlab.GitLabAPIAdapter.getCommit(GitLabAPIAdapter.java:37) at jigit.indexer.IndexingWorker.indexFromCommit(IndexingWorker.java:128) at jigit.indexer.IndexingWorker.indexRepoBranch(IndexingWorker.java:97) at jigit.indexer.IndexingWorker.handleBranchMode(IndexingWorker.java:66) at jigit.indexer.IndexingWorker.call(IndexingWorker.java:52) at jigit.indexer.IndexingWorker.call(IndexingWorker.java:20) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Server returned HTTP response code: 502 for URL: http://git.primaticsfinancial.com/api/v4/projects/private%2FEvolv/repository/commits/bbd27edbc34a5653a1089929d0f672eeee343904 at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1840) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) at api.client.http.ApiHttpRequester.parse(ApiHttpRequester.java:103) ... 15 more
-
repo owner *: Server returned HTTP response code: 502 for URL: *
It's not the error of the plugin. Some problems with your network or GitLab or nginx.
I have to reindex after few days to get all checkins available in Jigit Tab.
Sounds weird. Which version of the plugin do you use? How many branches do you have in your repo?
-
repo owner - changed status to invalid
-
reporter - attached Jigit_Plugin.JPG
-
reporter Hi Dmitrii,
I am going to reopen the case as we are still facing the same issue. I can see that a new version of Jigit plugin is available which has fixes of the same indexing issues.
Let me know try to update the plugin and I will get back to you.
Thanks Abid
-
reporter Hi,
I have updated the Jigit Plugin to the latest version and reindexed the repository but still I am facing the same issue. Please find the attached snapshots. You can see there are 2 commits appearing in the Development Panel but there is no checkins appearing in the Jigit tab. Could you please look into it and let me know if you need further information.
Abid
-
reporter - attached Development.JPG
-
reporter - attached JigitTab.JPG
-
reporter - changed status to open
Reopening the issue.
-
repo owner I don't know what the Development Panel is.
- What commits are you waiting to appear in Jigit Tab? Write their sha1, commit messages and branch names.
- Enable debug logging level for package jigit and collect related information from JIRA log.
-
reporter - changed status to resolved
Issue is resolved after updating the plugin to the newer version
- Log in to comment
Hi,
There are no limitations in the plugin. "Index All Branches" option should work as well as indexing of selected branches.
Please, enable debug logging level for package jigit and collect related information from JIRA log.
How to change logging level see https://confluence.atlassian.com/adminjiraserver073/logging-and-profiling-861253813.html#Loggingandprofiling-Logginglevels