Integrate Jigit with GitHub Enterprise

Issue #42 resolved
Former user created an issue

Hi,

I'm having some issues when attempting to configure the plugin with GitHub Enterprise.

I get the following Error: error: http://github.otpp.com/api/v3/groups/DevOps-Powershell/projects . See JIRA log for details.

The api call returns the following:

Cheers, Elias

Comments (15)

  1. Dmitrii Apanasevich repo owner

    Hi Elias,

    As far as I understood, you have tried to configure a group of repositories, right? How did you get the error? By pressing Test connection button?

    Could you provide me with the stacktrace of the error from JIRA log?

  2. Elias Tourani

    Hi Dmitrii,

    I did try to configure a group of repositories. I got this error when testing the connection.

    Here's what I see in the logs:

    2018-05-24 02:25:05,713 Caesium-3-3 ERROR ServiceRunner [jigit.indexer.JigitIndexer] JigitIndexer::execute java.io.FileNotFoundException: http://github.otpp.com/api/v3/groups/DevOps-Powershell/projects at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) at api.client.http.ApiHttpRequester.parse(ApiHttpRequester.java:93) at api.client.http.ApiHttpRequester.withResultOf(ApiHttpRequester.java:66) at api.client.http.ApiHttpRequester.withResultOf(ApiHttpRequester.java:58) at jigit.client.gitlab.GitLabGroupsAPI.repositories(GitLabGroupsAPI.java:31) at jigit.indexer.repository.RepoType$2.repositories(RepoType.java:35) at jigit.indexer.repository.RepoInfoFactoryImpl.getGitlabAPIAdapter(RepoInfoFactoryImpl.java:51) at jigit.indexer.repository.RepoInfoFactoryImpl.build(RepoInfoFactoryImpl.java:41) at jigit.indexer.IndexingWorkerFactoryImpl.build(IndexingWorkerFactoryImpl.java:46) at jigit.indexer.JigitIndexer.execute(JigitIndexer.java:39) at jigit.job.JigitIndexJob.execute(JigitIndexJob.java:33) at com.atlassian.sal.jira.scheduling.JiraPluginScheduler$JobDescriptor.runJob(JiraPluginScheduler.java:110) at com.atlassian.sal.jira.scheduling.JiraPluginScheduler.runJob(JiraPluginScheduler.java:80) at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153) at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118) at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:410) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:388) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282) at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65) at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59) at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34) at java.lang.Thread.run(Thread.java:745)

  3. Dmitrii Apanasevich repo owner

    Apparently, you are the first user with GitHub Enterprise.

    There ia a bug in a function of defining whether it's GitHub or GitLab. Jigit decides that you are using GitLab and throws the exception.

    I'll fix it.

  4. Dmitrii Apanasevich repo owner

    I'm ready to release a fixed version, but I cannot check whether it works properly with a GitHub Enterprise instance. I have no access to any instance.

    Are you still interested in Jigit? Could you help me with the testing? I can provide you with the new version and instructions. All you need to do is to install the add-on from provided file, edit repository settings and make sure that Jigit works as expected.

  5. Dmitrii Apanasevich repo owner

    Great!

    I've attached the new version which supports GitHub Enterprise. You have to install it, go to Jigit setting and explicitly select GitHub as a type of the host. Than, click Test connection and wait for synchronization of commits of DevOps-Powershell repositories.

  6. Elias Tourani

    Hi Dmitrii,

    I just finished testing it. I explicitly added Github and the connection test was successful. I also tested out a commit with the JIRA issue in the commit message and I can now see the commit details in JIRA under the jigit tab.

    Thanks for your assistance!

  7. Maggie Gu

    Hi @dmitry_apanasevich,

    I met this issue too after I upgrade Jigit to version 1.2.7. The Jigit works fine before I upgrade. Now it doesn' work.

    Could you please have a look?

    Thanks -Maggie

    2018-07-15 18:55:43,714 http-nio-8080-exec-87 ERROR *** 1135x4924896x3 19c1zi4 10.200.253.3 /rest/jigit/1.0/repo/test [jigit.resource.JigitAdminResource] An exception was occurred while testing a repository *****
    java.io.FileNotFoundException: http://gitlab.****.com//api/v4/projects/***%2F***/repository/branches/master
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
        at api.client.http.ApiHttpRequester.parse(ApiHttpRequester.java:103)
        at api.client.http.ApiHttpRequester.withResultOf(ApiHttpRequester.java:76)
        at api.client.http.ApiHttpRequester.withResultOf(ApiHttpRequester.java:63)
        at jigit.client.gitlab.GitLabRepositoryAPI.getBranch(GitLabRepositoryAPI.java:51)
        at jigit.indexer.api.gitlab.GitLabAPIAdapter.getHeadCommitSha1(GitLabAPIAdapter.java:52)
        at jigit.resource.JigitAdminResource.testRepo(JigitAdminResource.java:147)
        ... 3 filtered
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
        ... 13 filtered
        at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.doFilter(RestDelegatingServletFilter.java:154)
        ... 1 filtered
        at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.doFilter(RestDelegatingServletFilter.java:68)
        ... 41 filtered
        at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
        ... 53 filtered
        at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:80)
        ... 1 filtered
        at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:78)
        ... 16 filtered
        at com.atlassian.plugins.rest.module.servlet.RestSeraphFilter.doFilter(RestSeraphFilter.java:37)
        ... 20 filtered
        at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
        ... 10 filtered
        at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
        ... 4 filtered
        at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)
        ... 29 filtered
        at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
        ... 28 filtered
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        at java.lang.Thread.run(Thread.java:745)
    
  8. Log in to comment