GitLab issue tracking setup - SOLVED
已回答
When setting up issue tracking integration with GitLab...
- Is the Server URL https://gitlab.com?
- Is the Token my private API token found at https://gitlab.com/profile/account or is it a new access token I create at https://gitlab.com/profile/personal_access_tokens ?
- I've tried both kinds of tokens and in both cases when I click Test, PhpStorm comes back with "Read timed out" in an error dialog box.
I've tried other URLs, too:
- https://gitlab.com/<my username> - returns a 404 error
- https://gitlab.com/<group name> - returns a 404 error
- https://gitlab.com/<group name>/<project name> - returns a 404 error
- https://gitlab.com/users/sign_in - returns a 404 error
Edit: changed post title
请先登录再写评论。
Have the same problem in both Webstorm and RubyMine
It seems that this is not an IntelliJ bug, but an expected behaviour due to loong response times from `Gitlab` API.
Go to Preferences > Tools > Tasks and increase the timeout time to 15000.
It worked for me
There's a guide available for setting up Issue Tracker integration: https://confluence.jetbrains.com/display/PhpStorm/Integration+with+an+Issue+Tracking+System+in+PhpStorm
Unfortunately GitLab isn't supported officially yet and one would have to use "Generic" type of a issue tracking server.
OP is most likely using a 3rd party plugin: https://plugins.jetbrains.com/phpstorm/plugin/7319-gitlab-integration
If you're still facing the issue please let us know - we'll try to reproduce the same
Petros: Thanks, that did it!
For the record, to log in you should create a new Personal Access Token at https://gitlab.com/profile/personal_access_tokens so that you don't have to use your account's private token or password. (I don't know if those other two credentials even work because I didn't test them after setting a higher timeout value.)
Dmitry: I happened to have GitLab Projects installed, but it has nothing to do with issue tracking because as a test I uninstalled it and GitLab was still listed as a server option.
Apparently I'm wrong, GitLab integration is currently WIP and there's indeed an issue with a timeout: https://youtrack.jetbrains.com/issue/IDEA-166992
@Dmitry Tronin GitLab integration was there for years, its just seems a bit unattended and breaks now on then. With current mass migration to GitLab though, this shouldn't be the case any more.
Hello, my GitLab server has a specific port and with the the plugin cannot connect to the server, so, if I configure server as follows:
https://git.touchsystems.ch:30000 and put a token, which I created, I always get HTTP error 410 Gone on response of Test button click... Any idea what is wrong?
Unfortunately, it is hard to tell anything for sure before checking logs first. Could you please collect these? (Help > Collect Logs)