When running Jenkins behind an HTTPS proxy, everything said under JenkinsBehindProxy applies.
In addition, there are several more issues (to be explained better):
- Native git still requires a proper Java configuration which is counter-intuitive
- Vice versa ...
- Proxy authentication credentials
- Non-proxy hosts (when combining internal and external repositories)
- No plugin?
Some of the current behaviour may need reporting as a bug in Git client plugin.
To be able to access Github, It looks like one needs an environment variable:
https_proxy=http://NTDOMAIN\\user:password@some.proxy.net:1234/
Where is that read?
Does that have to be in addition to -Dhttps.... ?