Jira to Git integration Issue
Issue #61
invalid
Hi Team,
We are using Jira software 7.3.2 version(On premise server) and Gitlab (GitLab Community Edition) 8.15.4, Is integration is possible with your plugin. While configuration I am getting below error. error: https://api/v4/projects/https%3A%2F%2F%2FTest%2FTestProject%2F/repository/branches/master . See JIRA log for details.
Comments (35)
-
repo owner
-
reporter
Hi,
After using 1.2.6 version also I am getting same error, would you please suggest?
Thanks & Regards, Smriti Priya
-
repo owner
I'd recommend following the advice: to look through JIRA log to get error details.
-
repo owner
Could you also show the screenshot with your repo config?
-
reporter
Dmitrii,
Below is the screen shot:
[cid:image001.png@01D487FE.8E02D420]
Thanks & Regards, Smriti Priya
-
repo owner
Unfortunately, you haven't attached the screenshot.
-
hi
i have exactly the same problem
it does not matter what i fill in the form , it does not work , i tried many combination .... repository group different access tokes etc
see screenshots below
and here the java exception
-
i wonder about the urlencoded slash in the exception message ... i will try gitlab.com ... maybe its a problem with my selfhosted git ...
ah ok that is strange with gitlab.com it works , see below , maybe a problem with my selfhosted git ... or with subdomain routing ?
-
hmmm that is really weird ... on my selfhosted git i have to setup the project id instead of the path
any suggestion how to fix that ?
-
repo owner
Hi Matthias,
Everything is ok with urlencoded slash, it should be encoded as it's a part or repo name.
Maybe you have faced this issue ? Try to play with another repo without dots inside the name.
If you have nginx beign used with your Gitlab instance you can face this issue https://stackoverflow.com/questions/28684300/nginx-pass-proxy-subdirectory-without-url-decoding/37584637#37584637
-
ok now i have the problem that in the jigit table in the issue view the revisions link is rendered false and it gives me an 404 on the gitlab site .. so i have to set the path correctly the hack does not work
-
hey @dmitry_apanasevich
thx for quick response ...
yes maybe an issue with the dot in my username ... but on gitlab.com i have the dot in username too and it works (maybe an nignx config to fix that issue) i will try the following on my selfhosted gitlab instance:
- username without dots inside
- try access from jigit
-
repo owner
but on gitlab.com i have the dot in username too and it works (maybe an nignx config to fix that issue)
or you have another GitLab version.
the revisions link is rendered false and it gives me an 404 on the gitlab site
Please, try to remove the slash at the end of host name.
-
gitlab version is latest:
ok i tried a username without dots ... it does not work
i created a new user without dots .... see below
-
or repo
-
i guess the main problem is what i figured out below ... but i dont know why ... any suggestions with my gitlab config ?
this will work: (project id instead of path in url)
https://gitlab.mhertel.de/api/v4/projects/14/repository/branches/masterreturns:
this will not work
https://gitlab.mhertel.de/api/v4/projects/mhertel%2Fccva-go/repository/branches/masterthis returns a 404:
-
repo owner
I would assume that the cause of the problem is the slash, but the previous screenshot displays an error even with https://gitlab.mhertel.de/api/v4/groups/mhertel/projects.
Looks really strange. Sorry, but I have no idea what's wrong.
Try to open an issue here https://gitlab.com/gitlab-org/gitlab-ce/issues. I'd be grateful if you leave a link on it here.
-
repo owner
Hmm. I've just tried to go by URL you've left above and have got this:
UPD I've edited the image to hide your email.
-
okay i solved the issue .... the problem described above with the 404 error was the reason ...
i had an misconfiguration in my nginx config .... @dmitry_apanasevich you were right , the problem was the urlencoded slash was misinterpreted by nginx so the webserver responded with 404
-
repo owner
You are welcome :)
Please, leave a feedback about the plugin at marketplace page if you like it.
-
yes one more question ...
i made a commit to my repo with the correct issue key ... works fine ... and the tab jigit the commits appears ... but it is posible to set the state of the issue automatically to "in progress " ?
-
repo owner
is posible to set the state of the issue automatically to "in progress " ?
No, it's not possible. Because it's your custom logic. Other workflows use commits with issue key as a signal to close issue, for example here, on Bitbucket.
-
repo owner
@smritip what about about your problem? Have you found the solution? Sorry, we've littered your issue.
-
reporter
Dmitrii,
Still I am facing issue, please find the attach error.
Thanks & Regards, Smriti Priya
-
repo owner
@smritip, sorry, where is the attachment? Please, attach carefully the screenshot of repo settings and a part of JIRA log with the exception. I can't help you without this information.
-
reporter
- attached Error.png
-
reporter
- attached Jira Error.png
-
repo owner
Field Path should contain a repo name only. There should be Test/TestProject without sever URL
-
reporter
@Dmitri now connection is success but commit details not reflecting on Jira.
-
repo owner
Are there still no commits on Jigit tab? What was the commit message of expected commit?
-
reporter
Still commit message not reflecting in Jira.
-
repo owner
- changed status to invalid
-
repo owner
Have you read the plugin overview or wiki? Look: Jigit is an add-on for JIRA Server 7.0+ that provides an issue tab, which displays information about all commits referencing to the issue key. So, commit message should contain an issue key to have the commit displayed on the issue tabpage.
test is absolutely valueless message. How plugin will guess which issue is related to this commit?
-
reporter
Even after giving issue key also its not working.
-
repo owner
Do you have any error message related to Jigit in JIRA log?
- Log in to comment
Hi,
I think you've faced with the same problem as in issue 51
Try version 1.2.6
You can look through changes here: https://marketplace.atlassian.com/apps/1217129/jigit-github-and-gitlab-integration/version-history