• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

          [JSWSERVER-14382] Add support for Github:Enterprise

          GitHub enterprise support is now available as version 1.3 from the Atlassian Marketplace:

          Thanks to everyone who's helped get this feature out the door.

          Cheers, Justen
          Bitbucket product manager

          Justen Stepka [Atlassian] added a comment - GitHub enterprise support is now available as version 1.3 from the Atlassian Marketplace: https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-bitbucket-connector-plugin Thanks to everyone who's helped get this feature out the door. Cheers, Justen Bitbucket product manager

          I'm just going to put this out here: this is a thing of beauty and our users are delighted with it. We, of course, have a hailstorm of requests for improvements, but the basic thing itself works like a charm. Well done, chaps.

          Ashton Treadway added a comment - I'm just going to put this out here: this is a thing of beauty and our users are delighted with it. We, of course, have a hailstorm of requests for improvements, but the basic thing itself works like a charm. Well done, chaps.

          Ashton Treadway added a comment - - edited

          [EDITED TO NOT BE SAYING WRONG THINGS]

          Ashton Treadway added a comment - - edited [EDITED TO NOT BE SAYING WRONG THINGS]

          Any update on when this is going to go into production and be Official?

          Not that we're impatient for it.

          Ashton Treadway added a comment - Any update on when this is going to go into production and be Official? Not that we're impatient for it.

          Thanks Dusan, are these the correct changes?
          https://bitbucket.org/atlassian/jira-bitbucket-connector/compare/jira-dvcs-connector-parent-1.3-m4..jira-dvcs-connector-parent-1.3-m3

          So far, 1.3-m3 been working flawlessly. Looks like m4 should only be better.

          Mikael Fridh added a comment - Thanks Dusan, are these the correct changes? https://bitbucket.org/atlassian/jira-bitbucket-connector/compare/jira-dvcs-connector-parent-1.3-m4..jira-dvcs-connector-parent-1.3-m3 So far, 1.3-m3 been working flawlessly. Looks like m4 should only be better.

          DusanA added a comment -

          Hi,

          Another milestone release is ready for testing. It can be downloaded here 1.3-m4.

          Cheers,
          Dusan

          DusanA added a comment - Hi, Another milestone release is ready for testing. It can be downloaded here 1.3-m4 . Cheers, Dusan

          1.3-m3 is still throwing this error whenever we try to sync a repo:

          Sync Failed: There was a SQL exception thrown by the Active Objects library: Database: - name:MySQL - version:5.5.16-55-log - minor version:5 - major version:5 Driver: - name:MySQL-AB JDBC Driver - version:mysql-connector-java-5.1.10 ( Revision: ${svn.Revision} ) java.sql.SQLException: Column '''''primary_key_field''''' not found. –

          Ashton Treadway added a comment - 1.3-m3 is still throwing this error whenever we try to sync a repo: Sync Failed: There was a SQL exception thrown by the Active Objects library: Database: - name:MySQL - version:5.5.16-55-log - minor version:5 - major version:5 Driver: - name:MySQL-AB JDBC Driver - version:mysql-connector-java-5.1.10 ( Revision: ${svn.Revision} ) java.sql.SQLException: Column '''''primary_key_field''''' not found. –

          It comes down to SSL trust! had a shoddy CA so I imported the JIRA servers cert and trusted it and now all is fine so far... 1.3-m3.

          Mikael Fridh added a comment - It comes down to SSL trust! had a shoddy CA so I imported the JIRA servers cert and trusted it and now all is fine so far... 1.3-m3.

          I can do the first oAuth part fine and authorize the app, but when adding a DVCS account it fails.
          UI says:

          Error obtaining access token. Cannot access https://github.corp.net from Jira.

          if that helps at all... Let us know if we can give any more testing feedback if that helps.

          Mikael Fridh added a comment - I can do the first oAuth part fine and authorize the app, but when adding a DVCS account it fails. UI says: Error obtaining access token. Cannot access https://github.corp.net from Jira. if that helps at all... Let us know if we can give any more testing feedback if that helps.

          I tried 1.3-m3 from here on a VM of mine but couldn't get the oAuth to fly properly:
          https://maven.atlassian.com/content/repositories/atlassian-public/com/atlassian/jira/plugins/jira-dvcs-connector-plugin/1.3-m3/

          It reacted as though it could not contact the git server in some sort of verification stage... this was on a VM with the Github Enterprise server on the other end of VPN so a bit unsure what was going wrong and didn't have time to test it again.

          Mikael Fridh added a comment - I tried 1.3-m3 from here on a VM of mine but couldn't get the oAuth to fly properly: https://maven.atlassian.com/content/repositories/atlassian-public/com/atlassian/jira/plugins/jira-dvcs-connector-plugin/1.3-m3/ It reacted as though it could not contact the git server in some sort of verification stage... this was on a VM with the Github Enterprise server on the other end of VPN so a bit unsure what was going wrong and didn't have time to test it again.

            dhornik DusanA
            baed0ff7e7eb Keith Miller
            Votes:
            31 Vote for this issue
            Watchers:
            33 Start watching this issue

              Created:
              Updated:
              Resolved: