SIGINT-2299

[jahid1209]

Address the recommendations from the jenkins-infra team mentioned here.

[zaman-akib]

As per the requirements, users will pass HTTP_PROXY/http_proxy or HTTPS_PROXY/https_proxy (must use exact env variable name as we document these in the plugin docs) from Jenkinsfile or users will set these proxy details using these exact env variable names in their System environment variables and we will use those proxy to download bring-cli. Users will not set proxy through Jenkins Proxy Configuration.

Example Jenkinsfile -

pipeline {
    agent any
    environment {
        HTTPS_PROXY: 'https://example.proxy.com'
    }

    stages {
    // stages & steps here
    }
}

Please refer to this doc - https://documentation.blackduck.com/bundle/bridge/page/documentation/c_jenkins-additional-configs.html

That's why I believe we cannot replace the proxy related codes with Jekins proxy configuration. If we must update these then we need to confirm with PM.