Closed HadrienMP closed 8 years ago
Any clue what may be causing this ?
@HadrienMP Hi. Please excuse the late answer. What happens if you try to connect to Bitbucket from your build server directly, e.g. with cURL:
The cause for this issue might be that our plug-in does not respect your proxy settings. How do you configure these?
Hi, no need to worry ;). Right now my proxy is configured in "Internet Options" and in my maven settings.
I tried to build from my development desktop (windows 7). I tried cURL in "cmd" without any luck.
I tried with set https_proxy=https://myproxy:myport and --insecure in the cURL and I managed to get the json.
I see. I have to respect the https_proxy environment variable in the plug-in when doing connections to Bitbucket.
Would you be interested to beta-test this once I've implemented it? I could attach a SNAPSHOT to this issue.
Absolutely !
Hi,
I have a snapshot ready (see attached) which supports an HTTP proxy. Just configure the parameters like follows:
-Dhttp.proxyHost=http://localhost -Dhttp.proxyPort=9000
Looking forward to your feedback! Thanks sonar-bitbucket-plugin-1.1.4-SNAPSHOT.zip
Released with version 1.1.4
Sorry for the delay, I had no time to test the last weeks. I tried the new release without any luck. But maybe I'm still doing something wrong. I get the same error message.
I looked at the code and tried to find the warn message "Going to use proxy" in my maven build logs (in debug mode) but didn't find it. Am I looking at the right place ?
No problem. You should see this warning message, otherwise the proxy settings are not applied. Could you please make sure that you've specified the proxy settings like follows:
-Dhttp.proxyHost=http://localhost -Dhttp.proxyPort=9000
I set those variables it in the sonar.properties file (and in my environment variables) is it supposed to be enough ? Is the warn trace supposed to be in the sonar log or the maven log ?
I wasn't very specific about this. You have to add
-Dhttp.proxyHost=http://localhost -Dhttp.proxyPort=9000
to the command line with which you trigger Maven. You should then see the warning message in the Maven build log.
It works like a charm now ! Thanks !
Perfect, thanks for your feedback!
I'm not sure if I haven't configured something poorly, in doubt I'm adding this issue (it can be added to the documentation if it's a configuration issue)
I've configured my proxy in sonar and in maven settings but keep hitting a timeout. Do you have an idea about what I could have done wrong ?
You can find the stack trace below below :