We are using a hybrid approach with both cloud and on-premises solutions, where the proxies differ between cloud and on-prem environments. Currently, the Jenkins Git plugin only respects the globally configured Jenkins proxy, even when the Git global configuration is changed or when the http_proxy and https_proxy environment variables are set before a Git checkout.

This setup does not allow for the flexibility of using a different proxy configuration when performing Git operations on specific Jenkins nodes. To address this, we need the ability to bypass the global Jenkins proxy settings and use a custom proxy defined at the node level during Git checkouts. This will ensure that the appropriate proxy is used based on the environment, improving the flexibility.