At the moment, the Git plugin uses the HTTP Proxy from the Jenkins-Plugin-Manager site, if there's a proxy configured.

However we don't want to use that proxy for the git clone cases and from some nodes there's even no access to that proxy. So we'd like to see two features:

• Configure the Git plugin globally to use or not use the Jenkins-Plugin-Manager proxy (maybe with the option to provide an other proxy)
• On Source Code Management section of a job configuration: An additional behaviour to enable, disable or provide an other proxy. This could be part of the "Advanced clone behaviours" option.