Linky menu items not visible in dropdowns

Issue #9 resolved
Former user created an issue

Hi there, Am using Linky v2.3 Intellij 2016.2 running under Java 8

I cannot see any Linky menu items when I right click on a file which is managed inside BitBucket using Git.

Looking into the idea log, I can see this message repeated:

2016-07-20 08:42:35,935 [  18105]   INFO -            BitbucketReferences - Path '/myproject/mymodule' of git remote url 'ssh://git@my.bitbucketserver.com:7999/myproject/mymodule.git' matches Bitbucket Server repository path pattern but no base URI resolved

Any help would be appreciated.

Cheers

Comments (3)

  1. Daniil Penkin staff

    Hello,

    Thanks for trying Bitbucket Linky!

    That log message means that Linky tried but failed to reach Bitbucket Server using the URL guessed from your git remote URL: in case of Bitbucket Server Linky tries to guess its HTTP/S base URL and check it by querying the REST API.

    I assume that your Bitbucket Server instance runs not on 80 or 443 port. Moreover, given that it runs SSH server on port 7999, I assume you're running Bitbucket on default port 7992. The problem is that when git remote URL has SSH scheme, Linky only tries standard HTTP and HTTPS ports, i.e. 80 and 443. Maybe it's worth adding default port 7992 to the check list as well.

    I plan to add some configuration bits for Linky so that Bitbucket Server URL could be set manually in such cases.

    As a workaround, you could do one of the following to get Linky working:

    • use HTTP git clone URL instead of SSH — in that case Linky will know what port does Bitbucket listen for HTTP requests
    • run Bitbucket on port 80 or 443 — in that case Linky will find it
    • forward port 80 or 443 to the port you run Bitbucket on

    Please let me know if this helped.

    P.S. You can enable verbose logging for Linky by appending BitbucketReferences into Help → Debug Log Settings... dialog in IntelliJ. Linky will then log which URLs it tried to find Bitbucket Server's HTTP endpoint.

  2. Log in to comment