GitHub Integration Broken?

[Andrew Bradford]

I used to be able to add a GitHub repo to a JIRA onDemand project manually (put in github.com address, then go to GitHub and put in post-commit hook manually). Now there's a new automatic looking system in place, but it doesn't work.

After I put in my github.com address for the repo I want to link to my JIRA project, I'm offered to "Install post commit service". Regardless of if I choose that, I get HTTP 301 errors, too many redirects and my repo isn't associated with my project. I'm confused as to what I'm supposed to do. The old manual way worked, the new way doesn't.

[Andrew Ferguson · Accepted solution]

Hey Andrew,

I had the exact same problem & this turned out to be the solution:

The issue is actually with the OAuth settings set for GitHub. You can find those here:

https://github.com/account/applications

My Callback URL was set to "http://[MYJIRA].atlassian.net/secure/admin/GitHubOAuth2.jspa"

It actually needs to be set to "https://[MYJIRA].atlassian.net"

Ensure it's using https, as http will fail by redirecting you to your JIRA Dashboard when you try and add a GitHub Repo.

Once you've updated these settings, try adding your github repository again. I did this and it finally worked, repo's associated with the project and scanning began. Commits show up in my JIRA tickets now too.

If you're still having trouble, feel free to email me: andrew (WITHAGIANTATSYMBOL) metaforsoftware.com

Cheers,

--Andrew

[Andrew Bradford]

Awesome!! Thank you so much! My repo is now synced!

It was not at all clear that the href="https://{myjira}.atlassian.net%20">https://{myjira}.atlassian.net is the proper callback URL. That must have changed with the new GitHub repo linking plugin in OnDemand. My callback was set the same way yours was and everything was working fine until about 2 weeks ago. There needs to be an indicator that this has changed, for me who was used to use the old GitHub repo linking page, there was no easy to spot info about this.

It also appears that the automatically inserted post commit hook is now different. I'm not sure why, but that's not a problem for me.

[Paul Jarman]

Does the connector only work with hosted GitHub? We are using our own, internally hosted GitHub.

[Andrew Bradford]

I've tried both in Firefox and Chromium, on Debian Squeeze (my development platform). Both have errors, leading me to think it's not my browser's fault.