anchor.diff:  
   [[source-code]]
   
  -=== Git Repository Source Options
  +=== Git Source
   
   When the `*BuildConfig.spec.source.type*` is `*Git*`, a Git repository is
   required, and an inline Dockerfile is optional.
  
positive.code: 
  // end::using-a-proxy-for-git-cloning-1[]
  
  [[trusted-certificate-authorities]]
  ==== Trusted Certificate Authorities
  
  The set of TLS certificate authorities that are trusted during a `git clone`
  operation are built into the {product-title} infrastructure images.  If your Git
  server uses a self-signed certificate or one signed by an authority not trusted
  by the image, you can disable TLS  verification by setting the
  `*GIT_SSL_NO_VERIFY*` environment variable to *true* in the appropriate strategy
  section of your build configuration. You can use the
  xref:../dev_guide/environment_variables.adoc#overview[`oc set env`] command to
  manage `*BuildConfig*` environment variables.
  
  [[using-private-repositories-for-builds]]
  ==== Using Private Repositories for Builds
  
  Supply valid credentials to build an application from a private repository.
  
  Currently two types of authentication are supported: basic username-password
  and SSH key based authentication.
  
  [[basic-authentication]]
  ===== Basic Authentication
  
  Basic authentication requires either a combination of `username` and `password`,
  or a `token` to authenticate against the SCM server. A `CA certificate` file,
  or a `.gitconfig` file can be attached.
  
  A xref:../dev_guide/secrets.adoc#dev-guide-secrets[`*secret*`] is used to store your keys.
  
  . Create the `*secret*` first before using the username and password to access
  the private repository:
  +
  ====
  ----
  $ oc secrets new-basicauth basicsecret --username=USERNAME --password=PASSWORD
  ----
  ====
  
  .. To create a Basic Authentication Secret with a token:
  +
  ====
  ----
  $ oc secrets new-basicauth basicsecret --password=TOKEN
  ----
  ====
  
  .. To create a Basic Authentication Secret with a CA certificate file:
  +
  ====
  ----
  $ oc secrets new-basicauth basicsecret --username=USERNAME --password=PASSWORD --ca-cert=FILENAME
  ----
  ====
  
  .. To create a Basic Authentication Secret with a `.gitconfig` file:
  +
  ====
  ----
  $ oc secrets new-basicauth basicsecret --username=USERNAME --password=PASSWORD --gitconfig=FILENAME
  ----
  ====
  
  . Add the `*secret*` to the builder service account. Each build is run with
  the `builder` role, so you need to give it access your secret with the
  following command:
  +
  ====
  
negative.code:         name: "python-33-centos7:latest"
      type: "Source"
  ----
  ====
  
  [NOTE]
  ====
  You can also use the `*oc set build-secret*` command to set the secret on the
  existing build configuration:
  ----
  $ oc set build-secret --source bc/sample-build basicsecret
  ----
  ====
  xref:using-secrets-in-the-buildconfig[Defining Secrets in the
  BuildConfig] provides more information on this topic.
  
  [[gitconfig-file]]
  ===== Gitconfig File
  
  If the cloning of your application is dependent on a `.gitconfig` file
  you can create a secret that contains it, and then add
  it to the builder service account, and then your `BuildConfig`.
  
  
  To create a secret from a `.gitconfig` file:
  
  ====
  ----
  $ oc secrets new mysecret .gitconfig=path/to/.gitconfig
  ----
  ====
  
  [NOTE]
  ====
  SSL verification can be turned off, if `sslVerify=false` is set for the `http`
  section in your `.gitconfig` file:
  ----
  [http]
          sslVerify=false
  ----
  ====
  
  [[basic-authentication]]
  ===== Basic Authentication
  
  Basic authentication requires either a combination of `username` and `password`,
  or a `token` to authenticate against the SCM server.
  
  Create the `*secret*` first before using the username and password to access
  the private repository:
  
  ====
  ----
  $ oc secrets new-basicauth basicsecret --username=USERNAME --password=PASSWORD
  ----
  ====
  
  To create a Basic Authentication Secret with a token:
  
  ====
  ----
  $ oc secrets new-basicauth basicsecret --password=TOKEN
  ----
  ====
  
  [[ssh-key-authentication]]
  ===== SSH Key Authentication
  
  SSH Key Based Authentication requires a private SSH key.
  
  The repository keys are usually located in the `$HOME/.ssh/` directory, and are named
  `id_dsa.pub`, `id_ecdsa.pub`, `id_ed25519.pub`, or `id_rsa.pub` by default.
  Generate SSH key credentials with the following command:
  
  ====
  ----
  $ ssh-keygen -t rsa -C "your_email@example.com"
  ----
  