-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/add corporate proxy support #124
Feat/add corporate proxy support #124
Conversation
Hello, Thanks for approving this PR. Just to now, when do you plan to merge and to release it ? Thanks |
} | ||
throw new IllegalStateException( | ||
String.format("No server found with the name: %s", serverName)); | ||
} | ||
|
||
public static Map<String, Object> getProxyConfig () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could support https proxy settings..But i'm not sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a good point. In Jenkins plugin manager proxy configuration, serverUrl does not include protocol (http or https), and there is no field to specify the protocol to use.
Based on this configuration, we are not able to determine if it is http or https protocol. We could presume that if it is 80, use HTTP and 443 use HTTPS, but proxy port can still be 8443 or something else.
I think if we want to support both http and https, this plugin must have it's own proxy user settings and proxy support implementation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello, is it good for you ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is. I wish I would have write access here..meh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hope so !
Hello, do you have any update about who can merge this PR ? |
We've ran into this issue when issuing a scan. Any idea of when this will be released? |
I propose this PR in response of the following issue : https://issues.jenkins.io/browse/JENKINS-62779
The point is to support corporate proxy. Before calling GitlabApi, we retrieve proxy parameters from Plugin Manager configuration.
My code is based on gitlab4j-api proxy implementation.
Unfortunately, ProxyClientConfig does not support no_proxy parameter. At least, there is few chance to have multiple gitlab servers behind proxy and directly reachable.
About test : I didn't add any... but no tests have been broken. I did test the configuration on my Jenkins with this new version :
I do not have any environment to test with authenticated proxy.
Finally, feel free to propose any improvments, I'm kind of new here :)