try to use the plugin

Issue #20 wontfix
Former user created an issue


i ve done all the seetings needed in jira. The test connection worked, but when i reindex i got the message below (authorisation? should i generate the acess key by being admin ?) : <status><status-code>500</status-code><message>{"message":"401 Unauthorized"}</message><stack-trace>api.APIException: {"message":"401 Unauthorized"} at api.client.http.ApiHttpRequester.handleError( at api.client.http.ApiHttpRequester.parse( at api.client.http.ApiHttpRequester.withResultOf( at api.client.http.ApiHttpRequester.withResultOf( at jigit.client.gitlab.GitLabRepositoryAPI.branches( at jigit.indexer.api.gitlab.GitLabAPIAdapter.branches( at jigit.indexer.BranchesApiCall.branches( at jigit.indexer.RepoDataCleaner.clearRepoData( at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at$ResponseOutInvoker$1.invoke( at$1.intercept( at

thanks for your help

Comments (9)

  1. Dmitrii Apanasevich repo owner


    Problem looks strange. Had indexing been completed before you decided to re-index a repository? Did you see commits at tabpages or quantity of indexed commits at the settings page? Why did you decided to re-index a repository?

  2. eswary

    Hi i never indexed before. i just put all the parameters in jira and that s all. i can see the tabpages on my issue on jira but i don't see the commits

    as it doesn't seem to work i ve tried the indexation


  3. Dmitrii Apanasevich repo owner

    Ok. I see. I think you've configured your repository to index all branches. Right?

    Let's try to call GitLab API with curl ( Here is the pattern:

    curl -k -i --header "PRIVATE-TOKEN: {YOUR_TOKEN}" "{GITLAB_URL}/api/v3/projects/{REPO_NAME}/repository/branches"

    Put correct values into placeholders. The only challenge is to replace symbol / in repo name with %2F. You'll get something like this (I used gitlab-org/gitlab-ce as a repository name):

    curl -k -i --header "PRIVATE-TOKEN: my_own_secret_token" ""

    Does this command returns something different from 401 Unauthorized?

    Besides this, you can look for errors in JIRA log. I'm sure you'll find something related to Jigit.

  4. eswary

    Hi Dmitrii

    i 've tried the curl but i think the problem is that our gitlab is in our private network and not accessible from the web ?

    i'm at home an i can't access to the giblab repository. so even in, there is some kind of proxy to specify ?

    thanks for your help

  5. Dmitrii Apanasevich repo owner


    You have to check whether GitLab is accessible from JIRA server, not from your home. Curl comend that I've provede above shuld return a list of branches. If it this call works then Jigit will work too.

    I cannot help you with proxy setting or network setup.

    What about JIRA logs?

  6. Dmitrii Apanasevich repo owner


    Do you have any news? Have you managed to check GitLab availability with curl?

  7. Dmitrii Apanasevich repo owner


    I cannot offer a solution because I haven't got details about the problem you've faced.

    I need information from JIRA log. Grab it using keyword jigit.

    Then, you've mentioned that pressing Test connection button you get a successful response, right? In this case please login into your JIRA server (via SSH or somehow else) and execute curl command I've gave you above.

    Thats all at the moment.

    I look forward to hearing from you.

  8. Log in to comment