Moving this to Jenkins for further triage. Hypothetically the pods in Jenkins pipelines should be receiving the proxy env vars and pass those along.

Targeting 4.4.0 for investigation on the current master branch.

Still needs investigation for 4.5

@Jitendar can you check if you still have this one occuring on 4.4+ ?
as we made changes on the proxy setting propagation this should not occur.
You need an airgapped environment to try to reproduce it.

In the 4.4.0-0.nightly-2020-06-01-211921 proxy cluster,
If don't set workaround [1] for jenkins server, then pipeline build still could reproduce the bug issue.
After set workaround, the pipeline build will meet bug #1813217 issue.

This is not related to jenkins component, this related to the configuration of  build.config.openshift.io/cluster  which is not propagating the proxy env a it should on pod env variables, i guess
th doc here is actually not correct because it is not working https://docs.openshift.com/container-platform/4.2/builds/build-configuration.html
This is related to openshift component
Can someone please assign to the right team
Thank you

In http proxy cluster，common builds could retrive code from github both when build.config.openshift.io/cluster configures proxy to override the global proxy or not. Likewise only pipeline builds don't work.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days