anchor.diff:  build phases.
   <6> Additional default environment variable that will be added to
   every build.
  -<7> Labels to be applied to every image built. Users can override these in their `*BuildConfig*`.
  -<8> Build pods will only run on nodes with the `*key1=value2*` and `*key2=value2*` labels.
  -    Users can define a different set of `*nodeSelectors*` for their builds in which case these
  +<7> Labels to be applied to every image built. Users can override these in their `BuildConfig`.
  +<8> Build pods will only run on nodes with the `key1=value2` and `key2=value2` labels.
  +    Users can define a different set of `nodeSelectors` for their builds in which case these
       values will be ignored.
   <9> Build pods will have these annotations added to them.
  -<10> Sets the default resources to the build pod if the `*BuildConfig*` doesn't have related resource defined.
  -
  -====
  -
  -Restart the master service for the changes to take effect:
  -
  -====
  +<10> Sets the default resources to the build pod if the `BuildConfig` does not have related resource defined.
  +
  +====
  +
  +. Restart the master service for the changes to take effect:
  ++
   ----
   # systemctl restart atomic-openshift-master
   ----
  -====
   
   [[setting-global-build-overrides]]
   == Setting Global Build Overrides
   
  -To configure the `*BuildOverrides*` plug-in, add a configuration for it in the
  +To configure the `BuildOverrides` plug-in:
  +
  +. Add a configuration for it in the
   *_/etc/origin/master/master-config.yaml_* file on masters:
  -
  ++
   ====
   [source,yaml]
   ----
  
positive.code:             key2: value2
            annotations: <4>
              key1: value1
              key2: value2            
  ----
  <1> Force all builds to pull their builder image and any source images before
  starting the build.
  <2> Additional labels to be applied to every image built. Labels
  defined here take precedence over labels defined in `*BuildConfig*`.
  <8> Build pods will only run on nodes with the `*key1=value2*` and `*key2=value2*` labels.
      Users can define additional key/value labels to further constrain the set of nodes
      a build runs on, but the *node* must have at least these labels.
  <9> Build pods will have these annotations added to them.    
  ====
  
  Restart the master service for the changes to take effect:
  
  ====
  ----
  # systemctl restart atomic-openshift-master
  ----
  ====
  // end::installconfig_build_defaults_overrides[]
  
  
negative.code: 
  [NOTE]
  ====
  There are
  xref:../install_config/install/advanced_install.adoc#advanced-install-configuring-global-proxy[additional proxy settings]
  that can be
  xref:../install_config/build_defaults_overrides.adoc#setting-global-build-defaults[configured for builds] using Ansible parameters. For
  example:
  - The
  `openshift_builddefaults_git_http_proxy` and
  `openshift_builddefaults_git_https_proxy` parameters allow you to
  xref:../dev_guide/builds.adoc#using-a-proxy-for-git-cloning[use a proxy for git cloning]
  - The `openshift_builddefaults_http_proxy` and
  `openshift_builddefaults_https_proxy` parameters can make environment
  variables available to the
  xref:../dev_guide/builds.adoc#docker-strategy-environment[Docker build strategy]
  and
  xref:../dev_guide/builds.adoc#custom-strategy-environment[Custom build strategy]
  processes.
  ====
  
  [[manually-setting-global-build-defaults]]
  === Manually Setting Global Build Defaults
  
  To configure the `BuildDefaults` plug-in:
  
  . Add a configuration for it in the *_/etc/origin/master/master-config.yaml_*
   file on masters:
  +
  ====
  [source,yaml]
  ----
  