anchor.diff:  ====
   
   [[configuring-the-source-environment]]
  -=== Source Environment
  +=== Environment Variables
   
   There are two ways to make environment variables available to the
  -link:../architecture/core_concepts/builds_and_image_streams.html#builds[source build]
  +link:../architecture/core_concepts/builds_and_image_streams.html#source-build[source build]
   process and resulting \image: link:#environment-files[environment files] and
   link:#buildconfig-environment[*BuildConfig* environment] values.
   
  
positive.code: stored locally.
  ====
  
  
  [[custom-strategy-options]]
  
  
negative.code: stored locally.
  ====
  endif::openshift-origin[]
  
  [[custom-strategy-environment]]
  === Environment Variables
  
  To make environment variables available to the
  link:../architecture/core_concepts/builds_and_image_streams.html#custom-build[Custom build]
  process, you can add environment variables to the `*customStrategy*` definition
  of the `*BuildConfig*`.
  
  The environment variables defined there are passed to the pod that runs the
  custom build.
  
  For example, defining a custom HTTP proxy to be used during build:
  
  ====
  
  ----
  {
    "customStrategy": {
      ...
      "env": [
        {
          "name": "HTTP_PROXY",
          "value": "http://myproxy.net:5187/"
        }
      ]
    }
  }
  ----
  ====
  
  
  [[using-a-proxy-for-git-cloning]]
  
  