Support network proxy settings for local environments with Jenkins #136
Description
Currently, there is no way to specify network proxy settings when creating local Jenkins environment. It prevents Jenkins jobs from downloading dependencies as well as the failure of the Gradle-based tools. Bats tests that verify Maven tooling are failing as well when running as part of the seed pipeline.
Ideally, the proxy settings shall be specified as part of the start.sh script either as input parameters or script variables. They could also be picked up by the script from the environment of the machine it runs on.
Workaround is to modify Dockerfile to include http_proxy and https_proxy as ENV variables. Then add gradle.properties with proxy settings and code to copy it to the proper location in the init.gradle script. Similar changes need to be done for Maven, though at that stage we have preferred to disable testing as a part of the seed pipeline altogether as we don't use Maven.