anchor.diff:  $ oc secrets new mysecret ca.crt=path/to/certificate .gitconfig=path/to/.gitconfig
   ----
   ====
  -
  ++
   [NOTE]
   ====
  -Please note that SSL verification can be turned off, if `sslVerify=false` is set
  -for the `http` section in your `.gitconfig` file:
  +SSL verification can be turned off, if `sslVerify=false` is set for the `http`
  +section in your `.gitconfig` file:
   ----
   [http]
           sslVerify=false
   ----
   ====
   
  -. Add the `*secret*` to the builder service account. Each build is run with
  +.  Add the `*secret*` to the builder service account. Each build is run with the
   `serviceaccount/builder` role, so you need to give it access your secret with
   following command:
  -
   +
   ====
   ----
  
positive.code: [[other-authentication]]
  ===== Other
  
  In case the cloning of your application is dependent on a `CA certificate`, `.gitconfig`
  file or both, you can create a secret that contains them, add it to the builder service
  account and then your `BuildConfig`.
  
  . Create desired type of `*secret*`:
  
  
negative.code: ----
  ====
  
  .  Add the `*secret*` to the `*BuildConfig*`:
  
  ====
  ----
  source:
    git:
      uri: https://github.com/openshift/nodejs-ex.git
    secrets:
      - secret:
          name: "mysecret"
    type: Git
  ----
  ====
  
  link:builds.html#using-secrets-in-the-buildconfig[Defining Secrets in the
  BuildConfig] provides more information on this topic.
  
  [[dockerfile-source]]
  
  